Triple
T30087233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inferior colliculus |
E764631
|
entity |
| Predicate | locatedCaudalTo |
P4527
|
FINISHED |
| Object | superior colliculus |
—
|
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: superior colliculus | Statement: [inferior colliculus, locatedCaudalTo, superior colliculus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedCaudalTo Context triple: [inferior colliculus, locatedCaudalTo, superior colliculus]
-
A.
locatedMedialTo
Indicates that one entity is positioned toward the midline of the body relative to another entity.
-
B.
caudalSpineLocation
Indicates the anatomical position or region where the caudal (tail) spine is located on an organism.
-
C.
locatedAfter
chosen
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
D.
locatedBehind
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
-
E.
locatedAtBaseOf
Indicates that one entity is positioned at or near the bottom or lowest supporting part of 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: April 29, 2026, 7:04 p.m.