Triple
T31535236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | locus coeruleus |
E804585
|
entity |
| Predicate | situatedLateralTo |
P31095
|
FINISHED |
| Object | fourth ventricle |
—
|
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: fourth ventricle | Statement: [locus coeruleus, situatedLateralTo, fourth ventricle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedLateralTo Context triple: [locus coeruleus, situatedLateralTo, fourth ventricle]
-
A.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
isLocatedToThe
Indicates a spatial relationship where one entity is positioned in a specific directional orientation relative to another entity.
-
C.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
D.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
E.
locatedMedialTo
Indicates that one entity is positioned toward the midline of the body relative to another entity.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:03 p.m.