Triple
T23342610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Ridge route |
E591773
|
entity |
| Predicate | typicalCamp2Elevation |
P151938
|
FINISHED |
| Object | approximately 6400 m |
—
|
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 6400 m | Statement: [Southeast Ridge route, typicalCamp2Elevation, approximately 6400 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCamp2Elevation Context triple: [Southeast Ridge route, typicalCamp2Elevation, approximately 6400 m]
-
A.
campElevation
Indicates the elevation or height above sea level at which a camp is located.
-
B.
typicalCamp1Altitude_m
Indicates the usual or characteristic altitude, in meters, at which the first camp in a sequence of camps is located.
-
C.
typicalHighCampElevation
Indicates the usual or characteristic elevation at which a high camp is established for an activity such as mountaineering or expedition climbing.
-
D.
typicalCamp4Altitude_m
Indicates the altitude in meters that is typically associated with a mountain’s Camp 4 location.
-
E.
typicalCamp3Altitude_m
Indicates the usual elevation, in meters, at which the third camp in a sequence of camps is located.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198334dec819081c432b434eb3ba5 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:18 p.m.