Triple
T23342723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp II (South Col route, Mount Everest) |
E591776
|
entity |
| Predicate | aboveSeaLevelCategory |
P35392
|
FINISHED |
| Object | high altitude |
—
|
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: high altitude | Statement: [Camp II (South Col route, Mount Everest), aboveSeaLevelCategory, high altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboveSeaLevelCategory Context triple: [Camp II (South Col route, Mount Everest), aboveSeaLevelCategory, high altitude]
-
A.
emergedAboveSeaLevel
Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
-
B.
aboveSeaLevelSegments
Indicates that the referenced segments are located at elevations higher than sea level.
-
C.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
D.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
-
E.
altitudeCategory
chosen
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983431f08190b0078728d44872a8 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.