Triple
T21853938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | entorhinal cortex |
E539573
|
entity |
| Predicate | majorOutputPathwayFrom |
P122717
|
FINISHED |
| Object | hippocampus |
—
|
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: hippocampus | Statement: [entorhinal cortex, majorOutputPathwayFrom, hippocampus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorOutputPathwayFrom Context triple: [entorhinal cortex, majorOutputPathwayFrom, hippocampus]
-
A.
majorRouteTo
chosen
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
B.
hasPathway
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
C.
secondMajorOutput
Indicates that an entity serves as the second most important or secondary primary output produced by another entity or process.
-
D.
outputsTo
Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
-
E.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0bd5ba9288190af962117124f6483 |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.