Triple
T23490051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson's 1610–1611 voyage to Hudson Bay |
E570645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arctic exploration voyage |
C6950
|
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 voyage Context triple: [Hudson's 1610–1611 voyage to Hudson Bay, instanceOf, Arctic exploration voyage]
-
A.
Arctic exploration
Arctic exploration is the systematic investigation and traversal of the Arctic region to discover, map, understand, and utilize its geography, climate, ecosystems, and resources.
-
B.
exploration voyage
chosen
An exploration voyage is a journey undertaken to discover, investigate, and document unknown or little-known places, phenomena, or knowledge.
-
C.
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.
-
D.
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.
-
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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:04 p.m.