Triple
T26837838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luge at the 2014 Winter Olympics |
E675685
|
entity |
| Predicate | trackStartElevation |
P92412
|
FINISHED |
| Object | 1214 m |
—
|
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: 1214 m | Statement: [Luge at the 2014 Winter Olympics, trackStartElevation, 1214 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackStartElevation Context triple: [Luge at the 2014 Winter Olympics, trackStartElevation, 1214 m]
-
A.
typicalStartElevation
Indicates the usual or characteristic elevation at which something (such as a route, feature, or activity) typically begins.
-
B.
trailheadElevation
chosen
Indicates the elevation at which a trail begins, typically measured at its starting point or trailhead.
-
C.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
D.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
E.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:05 a.m.