Triple
T20632091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1924 British Mount Everest expedition |
E506979
|
entity |
| Predicate | highestCampAltitudeMetres |
P140841
|
FINISHED |
| Object | 8170 |
—
|
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: 8170 | Statement: [1924 British Mount Everest expedition, highestCampAltitudeMetres, 8170]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestCampAltitudeMetres Context triple: [1924 British Mount Everest expedition, highestCampAltitudeMetres, 8170]
-
A.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
D.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
E.
elevationOfHighestPeak_ft
Indicates the height, in feet, of the tallest peak associated with the given entity.
- F. None of above. chosen
Provenance (4 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0bdcd88190a59d68e03370b271 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.