Triple
T38491741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ascent of the Matterhorn (article and earlier accounts) |
E918070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountaineering narrative |
C11713
|
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 narrative Context triple: [The Ascent of the Matterhorn (article and earlier accounts), instanceOf, mountaineering narrative]
-
A.
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.
-
B.
mountaineering book
chosen
A mountaineering book is a written work that explores climbing expeditions, techniques, history, or personal narratives related to ascending mountains and high-altitude environments.
-
C.
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.
-
D.
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.
-
E.
mountaineering tradition
Mountaineering tradition is the set of shared practices, values, stories, and ethical norms that shape how climbers approach, experience, and pass down the culture of climbing high mountains.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.