Triple
T22589421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1913 Denali expedition |
E564899
|
entity |
| Predicate | hasHighestElevationReached |
P140570
|
FINISHED |
| Object | approximately 20,320 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 20,320 feet | Statement: [1913 Denali expedition, hasHighestElevationReached, approximately 20,320 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestElevationReached Context triple: [1913 Denali expedition, hasHighestElevationReached, approximately 20,320 feet]
-
A.
highestAltitudeReachedBy
Indicates the maximum altitude that a given entity has ever attained.
-
B.
highestLatitudeReached
Indicates the maximum latitude that an entity has ever reached during its movement or existence.
-
C.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
D.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
-
E.
highestAltitudeReachedFeet
chosen
Indicates the maximum altitude, measured in feet, that an entity has reached.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615f63788190acf776b313f0794a |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:48 p.m.