Triple
T3302257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin expedition |
E69362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arctic exploration expedition |
C1348
|
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 expedition Context triple: [Franklin expedition, instanceOf, Arctic exploration expedition]
-
A.
exploration voyage
An exploration voyage is a journey undertaken to discover, investigate, and document unknown or little-known places, phenomena, or knowledge.
-
B.
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.
-
C.
over-ice surface expedition
An over-ice surface expedition is a planned journey across frozen terrain—such as sea ice, glaciers, or ice sheets—using surface travel methods like skis, sleds, or specialized vehicles to conduct exploration, research, or transit.
-
D.
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.
-
E.
maritime expedition
chosen
A maritime expedition is an organized sea voyage undertaken for a specific purpose such as exploration, research, trade, or military objectives, typically involving specialized vessels, crew, and logistical planning.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.