Triple
T4764869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raid on Rochefort (1757) |
E105783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British amphibious 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: British amphibious expedition Context triple: [Raid on Rochefort (1757), instanceOf, British amphibious expedition]
-
A.
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.
-
B.
amphibious invasion
An amphibious invasion is a coordinated military operation in which armed forces assault a hostile or potentially hostile shore by deploying troops, vehicles, and equipment from the sea onto land.
-
C.
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.
-
D.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
E.
United Kingdom defence initiative
The United Kingdom defence initiative is a strategic program encompassing policies, capabilities, and collaborative efforts designed to protect the UK's national security interests and enhance its military readiness at home and abroad.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:21 p.m.