Triple
T7876201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British southern strategy |
E182860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British war strategy |
C17833
|
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 war strategy Context triple: [British southern strategy, instanceOf, British war strategy]
-
A.
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.
-
B.
British offensive
chosen
A British offensive is a coordinated military campaign initiated by British armed forces to attack and weaken enemy positions, gain territory, or achieve specific strategic objectives.
-
C.
World War II military plan
A World War II military plan is a strategically designed, time-bound set of coordinated operations and resource allocations intended to achieve specific political and military objectives within the context of the global conflict.
-
D.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:57 p.m.