Triple
T28325904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingraham Direct route |
E717406
|
entity |
| Predicate | typicalSummitElevation |
P14507
|
FINISHED |
| Object | 14,411 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: 14,411 feet | Statement: [Ingraham Direct route, typicalSummitElevation, 14,411 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSummitElevation Context triple: [Ingraham Direct route, typicalSummitElevation, 14,411 feet]
-
A.
typicalSummitTarget
Indicates that something is a usual or characteristic objective or destination associated with reaching a summit.
-
B.
summitElevation
chosen
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
typicalSummitLocation
Indicates that a location is commonly or characteristically used as the site where a summit (such as a meeting or peak event) takes place.
-
D.
hasSummitElevationApprox
Indicates that an entity has an approximate elevation value for its summit or highest point.
-
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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
Created at: April 28, 2026, 12:28 a.m.