Triple
T2685925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crested Butte Mountain Resort |
E57484
|
entity |
| Predicate | topElevation |
P19320
|
FINISHED |
| Object | approximately 12,162 feet |
—
|
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: approximately 12,162 feet | Statement: [Crested Butte Mountain Resort, topElevation, approximately 12,162 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topElevation Context triple: [Crested Butte Mountain Resort, topElevation, approximately 12,162 feet]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
C.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
D.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9ef2fe0819082bbe746ca682a7e |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.