Triple
T17328939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gressoney-La-Trinité |
E420761
|
entity |
| Predicate | highestSkiLiftElevation |
P75294
|
FINISHED |
| Object | over 3200 metres above sea level |
—
|
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: over 3200 metres above sea level | Statement: [Gressoney-La-Trinité, highestSkiLiftElevation, over 3200 metres above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestSkiLiftElevation Context triple: [Gressoney-La-Trinité, highestSkiLiftElevation, over 3200 metres above sea level]
-
A.
skiAreaElevationMax
chosen
Indicates the maximum elevation, typically in meters or feet, reached within a ski area.
-
B.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
D.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
E.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d50b308190a255874a9b8f3cd3 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.