Triple
T34091964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dentate gyrus |
E874320
|
entity |
| Predicate | receivesInputVia |
P179197
|
FINISHED |
| Object | perforant path |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: perforant path | Statement: [dentate gyrus, receivesInputVia, perforant path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesInputVia Context triple: [dentate gyrus, receivesInputVia, perforant path]
-
A.
receivesInputType
Indicates that an entity takes or accepts another entity as its input type in a process, function, or interaction.
-
B.
receptorInput
Indicates that a receptor receives or is provided with an input signal or stimulus from another entity.
-
C.
inputIs
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
D.
inputAccess
Indicates that one entity has the ability or permission to provide, modify, or otherwise interact with the input of another entity or system.
-
E.
providesInputFor
chosen
Indicates that one entity supplies data, resources, or material that are used as input by another entity or process.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:52 a.m.