Triple
T31544605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red nucleus |
E804841
|
entity |
| Predicate | locatedRostralTo |
P203581
|
FINISHED |
| Object | substantia nigra |
E229730
|
NE 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: substantia nigra | Statement: [red nucleus, locatedRostralTo, substantia nigra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedRostralTo Context triple: [red nucleus, locatedRostralTo, substantia nigra]
-
A.
locatedMedialTo
Indicates that one entity is positioned toward the midline of the body relative to another entity.
-
B.
locatedInHeadTempleRegion
Indicates that something is situated within the geographic or administrative region associated with the head temple.
-
C.
cephaliumPosition
Indicates the spatial placement of a cephalium in relation to the rest of the organism or structure it is part of.
-
D.
rostrumFunction
Indicates the functional role or purpose that a rostrum serves in relation to an entity or process.
-
E.
locatedOnFront
Indicates that one entity is positioned on the front side or face of another entity.
- F. None of above. chosen
Provenance (5 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01a9e333fc819087d583ff319be0b3 |
completed | May 11, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79bf231881909baf1c87470ee6b9 |
completed | June 12, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_6a01a877c9e08190b0678618d3533286 |
completed | May 11, 2026, 9:59 a.m. |
| PDg | Predicate description generation | batch_6a01a9e27adc81908b90db24e93f3be0 |
completed | May 11, 2026, 10:05 a.m. |
Created at: April 30, 2026, 10:07 p.m.