Triple
T25344864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainier Mountaineering Inc. |
E635517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountaineering school |
C23657
|
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 school Context triple: [Rainier Mountaineering Inc., instanceOf, mountaineering school]
-
A.
mountaineering education program
chosen
A mountaineering education program is a structured course of instruction that teaches individuals the technical skills, safety practices, and environmental awareness needed for responsible and effective mountain travel and climbing.
-
B.
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.
-
C.
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.
-
D.
mountaineering partnership
A mountaineering partnership is a collaborative relationship between climbers who share responsibility, risk, decision-making, and support to safely and effectively achieve objectives in the mountains.
-
E.
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.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:34 p.m.