Triple
T16314466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goûter Corridor |
E396138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountaineering hazard |
C30839
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: mountaineering hazard Context triple: [Goûter Corridor, instanceOf, mountaineering hazard]
-
A.
mountaineering feature
chosen
A mountaineering feature is any distinct natural or artificial element of mountainous terrain—such as ridges, faces, couloirs, or fixed anchors—that significantly influences route selection, difficulty, and safety in climbing and alpine travel.
-
B.
mountaineering expedition
A mountaineering expedition is an organized journey by a team to plan, approach, and ascend challenging mountain terrain, managing technical, environmental, and logistical risks to reach specific climbing objectives.
-
C.
mountaineering achievement
A mountaineering achievement is a notable accomplishment in climbing, such as summiting a peak, establishing a new route, or completing a challenging ascent under significant physical and environmental demands.
-
D.
alpine climbing area
An alpine climbing area is a high-altitude mountain environment offering established routes on rock, snow, and ice, typically requiring technical gear, route-finding skills, and awareness of rapidly changing weather and objective hazards.
-
E.
mountaineer
A mountaineer is an individual who climbs mountains, often using specialized skills and equipment to navigate challenging and high-altitude terrain.
- F. None of above.
Provenance (1 batch)
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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.