Triple
T28588919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Polish winter Broad Peak expedition |
E723587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish mountaineering 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: Polish mountaineering expedition Context triple: [2013 Polish winter Broad Peak expedition, instanceOf, Polish mountaineering 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.
French polar expedition
A French polar expedition is an organized scientific and exploratory journey led or sponsored by French institutions to study and traverse the Arctic or Antarctic regions under extreme environmental conditions.
-
C.
Antarctic expedition support group
An Antarctic expedition support group is an organization that provides logistical, technical, medical, and administrative assistance to plan, supply, coordinate, and sustain scientific or exploratory missions in Antarctica.
-
D.
multinational expedition
A multinational expedition is a coordinated journey or mission involving participants, resources, and leadership from multiple countries working together toward shared exploratory, scientific, or strategic objectives.
-
E.
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.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:19 a.m.