Triple
T3962607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Buttress route |
E85939
|
entity |
| Predicate | typicalBaseCampElevation |
P40318
|
FINISHED |
| Object | about 2200 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: about 2200 m | Statement: [West Buttress route, typicalBaseCampElevation, about 2200 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBaseCampElevation Context triple: [West Buttress route, typicalBaseCampElevation, about 2200 m]
-
A.
typicalBaseCampAltitude_m
chosen
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
B.
typicalCamp1Altitude_m
Indicates the usual or characteristic altitude, in meters, at which the first camp in a sequence of camps is located.
-
C.
typicalCamp4Altitude_m
Indicates the altitude in meters that is typically associated with a mountain’s Camp 4 location.
-
D.
typicalBaseCampArea
Indicates that a location is the usual or standard area used as a base camp for an activity, expedition, or operation.
-
E.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.