Triple
T29760033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Himalayan Committee |
E753737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountaineering committee |
C19552
|
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 committee Context triple: [Joint Himalayan Committee, instanceOf, mountaineering committee]
-
A.
mountaineering club
chosen
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.
-
B.
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.
-
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 museum
A mountaineering museum is a cultural institution that collects, preserves, and exhibits artifacts, stories, and educational materials related to the history, techniques, equipment, and notable figures of mountain climbing and alpine exploration.
-
E.
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.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:32 p.m.