Triple
T37146833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Train |
E920261
|
entity |
| Predicate | terminusAltitude |
P21269
|
FINISHED |
| Object | high-altitude station at Latour-de-Carol-Enveitg |
—
|
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: high-altitude station at Latour-de-Carol-Enveitg | Statement: [Yellow Train, terminusAltitude, high-altitude station at Latour-de-Carol-Enveitg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusAltitude Context triple: [Yellow Train, terminusAltitude, high-altitude station at Latour-de-Carol-Enveitg]
-
A.
locatedAtAltitude
chosen
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
hopAltitude
Indicates the vertical distance or height reached by an entity during a hop or jumping motion.
-
C.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
D.
separationAltitude
Indicates the altitude at which two entities diverge or become separated from one another.
-
E.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:15 p.m.