Triple
T506562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Whitney Trail |
E10514
|
entity |
| Predicate | elevationGain |
P6813
|
FINISHED |
| Object | over 6,000 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: over 6,000 feet | Statement: [Mount Whitney Trail, elevationGain, over 6,000 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationGain Context triple: [Mount Whitney Trail, elevationGain, over 6,000 feet]
-
A.
elevationChange
chosen
Indicates a change in vertical position or altitude between two points or states.
-
B.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
C.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
D.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
E.
topographicProminence
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f14c83f08190b1028f4929866db4 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.