Triple
T8745937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coleman–Deming route |
E207827
|
entity |
| Predicate | typicalStartingElevation |
P37604
|
FINISHED |
| Object | approximately 3,700 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 3,700 feet | Statement: [Coleman–Deming route, typicalStartingElevation, approximately 3,700 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartingElevation Context triple: [Coleman–Deming route, typicalStartingElevation, approximately 3,700 feet]
-
A.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
B.
typicalAscentStartPoint
chosen
Indicates the usual or most common location from which an ascent or climb is begun.
-
C.
elevationMinFeet
Indicates the minimum elevation of an entity or location, measured in feet.
-
D.
elevationMinApprox
Indicates an approximate value for the minimum elevation associated with an entity or location.
-
E.
typicalHighCampElevation
Indicates the usual or characteristic elevation at which a high camp is established for an activity such as mountaineering or expedition climbing.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d745e0081909cab216593d5c01b |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.