Triple
T6236044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex-Raleigh Expedition to the Azores |
E139480
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English naval campaign |
C10942
|
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 naval campaign Context triple: [Essex-Raleigh Expedition to the Azores, instanceOf, English naval campaign]
-
A.
Royal Navy operation
chosen
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.
-
B.
naval theatre of war
A naval theatre of war is a maritime region, including its adjacent coastal areas and airspace, where naval forces conduct coordinated military operations during an armed conflict.
-
C.
battle of the Second Anglo-Dutch War
A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict over maritime trade and colonial dominance.
-
D.
battle of the Second Anglo-Dutch War
A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict for maritime and commercial supremacy.
-
E.
Royal Navy warship
A Royal Navy warship is a commissioned naval vessel of the United Kingdom designed, armed, and operated for maritime defense, power projection, and support of national interests at sea.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:23 p.m.