Triple
T15922024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col du Galibier |
E386114
|
entity |
| Predicate | tunnelElevation |
P221
|
FINISHED |
| Object | 2556 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: 2556 m | Statement: [Col du Galibier, tunnelElevation, 2556 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelElevation Context triple: [Col du Galibier, tunnelElevation, 2556 m]
-
A.
elevationConnection
Indicates a relationship where one entity is linked to another through a change or difference in elevation, such as a vertical or sloped connection between their heights or levels.
-
B.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
trailheadElevation
Indicates the elevation at which a trail begins, typically measured at its starting point or trailhead.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.