Triple
T29699669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 K2 belay |
E751446
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountaineering event |
C3516
|
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 event Context triple: [1953 K2 belay, instanceOf, mountaineering event]
-
A.
mountaineering expedition
chosen
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.
-
B.
mountaineering feature
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.
-
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.
mountaineering award
A mountaineering award is a formal recognition given to individuals or groups for notable achievements, skill, courage, or contributions in the field of climbing and high-altitude exploration.
-
E.
mountaineering club
A mountaineering club is an organized group of individuals who share resources, training, and coordinated activities to safely plan and undertake climbing and high-altitude expeditions.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:22 p.m.