Triple
T8711602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 British Mount Everest expedition |
E206789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Everest expedition |
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: Everest expedition Context triple: [1953 British Mount Everest expedition, instanceOf, Everest expedition]
-
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.
1968 expedition
A 1968 expedition is a historically situated journey or organized exploration undertaken in the year 1968, typically involving a specific objective such as scientific research, geographic discovery, or cultural investigation.
-
C.
Mir expedition
The Mir expedition class represents a long-duration crewed mission to the Mir space station, encompassing its objectives, crew, timeline, activities, and outcomes.
-
D.
overland expedition
An overland expedition is a long-distance journey across remote or challenging terrain, typically using rugged vehicles or pack animals, focused on exploration, self-sufficiency, and adventure rather than speed or directness of route.
-
E.
Age of Discovery expedition
An Age of Discovery expedition is a state- or crown-sponsored maritime voyage undertaken between the 15th and 17th centuries to explore unknown regions, establish trade routes, claim territories, and gather scientific and geographic knowledge.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.