Triple
T25532279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barentsz’s Arctic expeditions |
E639953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arctic exploration campaign |
C36289
|
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: Arctic exploration campaign Context triple: [Barentsz’s Arctic expeditions, instanceOf, Arctic exploration campaign]
-
A.
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.
-
B.
Arctic exploration
chosen
Arctic exploration is the systematic investigation and traversal of the Arctic region to discover, map, understand, and utilize its geography, climate, ecosystems, and resources.
-
C.
American polar expedition
An American polar expedition is a government- or privately-sponsored journey by U.S.-based explorers to the Arctic or Antarctic regions, typically undertaken for scientific research, geographic exploration, or strategic purposes under extreme environmental conditions.
-
D.
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.
-
E.
Russian naval expedition
A Russian naval expedition is a state-organized maritime operation undertaken by the Russian Navy for purposes such as exploration, power projection, military engagement, or strategic presence beyond home waters.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:15 p.m.