Triple
T37936214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Polish winter K2 expedition |
E946357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish national expedition |
C66183
|
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 national expedition Context triple: [2018 Polish winter K2 expedition, instanceOf, Polish national expedition]
-
A.
Austrian expedition
An Austrian expedition is an organized journey or mission, typically sponsored or led by Austrian institutions or individuals, undertaken to explore, research, or achieve specific objectives in distant or challenging environments.
-
B.
Norwegian polar expedition
A Norwegian polar expedition is an organized journey, typically led by Norwegian explorers or institutions, to explore, study, or traverse the Arctic or Antarctic regions under extreme polar conditions.
-
C.
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.
-
D.
Danish expedition
A Danish expedition is an organized journey or voyage initiated by Danish individuals or institutions, typically for purposes such as exploration, scientific research, cultural exchange, or historical commemoration.
-
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. chosen
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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.