Triple
T15208128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Northern Expedition |
E363442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arctic exploration |
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 Context triple: [Great Northern Expedition, instanceOf, Arctic exploration]
-
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.
era of polar exploration
The era of polar exploration was a historical period, roughly from the late 19th to early 20th century, marked by intense international efforts to discover, map, and scientifically study the Arctic and Antarctic regions, often under extreme and perilous conditions.
-
C.
Arctic settlement
An Arctic settlement is a small, often remote community located within the Arctic region, adapted to extreme cold, seasonal darkness, and fragile polar ecosystems while supporting human habitation and local economic activities.
-
D.
Arctic organization
An Arctic organization is an entity dedicated to studying, managing, or advocating for the Arctic region’s environment, communities, resources, and geopolitical interests.
-
E.
Arctic exploration patron
An Arctic exploration patron is an individual or organization that funds, supports, and advocates for expeditions and research in the Arctic region, often driven by scientific, strategic, environmental, or philanthropic interests.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:11 a.m.