Triple
T14478743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Supply mission to Jamestown |
E359045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English maritime 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: English maritime expedition Context triple: [Third Supply mission to Jamestown, instanceOf, English maritime expedition]
-
A.
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.
-
B.
British expedition
A British expedition is an organized journey or voyage undertaken by individuals or groups from Britain, typically for purposes such as exploration, scientific research, military objectives, or cultural exchange.
-
C.
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.
-
D.
British navigator
A British navigator is a seafarer or explorer from Britain skilled in charting courses, using navigational instruments, and guiding ships safely across seas and oceans.
-
E.
Royal Navy operation
A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.