Triple
T30087222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | optic tract |
E764630
|
entity |
| Predicate | synapsesAt |
P168434
|
FINISHED |
| Object | lateral geniculate nucleus |
—
|
NE NERFINISHED |
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: lateral geniculate nucleus | Statement: [optic tract, synapsesAt, lateral geniculate nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synapsesAt Context triple: [optic tract, synapsesAt, lateral geniculate nucleus]
-
A.
connectsTerminus
Indicates that one entity serves as a terminus that is directly linked or joined to another entity.
-
B.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
terminusConnectsTo
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
-
D.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
E.
nearSiteOf
Indicates that one entity is located in close physical proximity to the site or location associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d6d35588190bf7b5ea2889ad6b8 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:04 p.m.