Triple
T27459416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Southern strategy during the American Revolutionary War |
E692690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British war plan |
C41950
|
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 plan Context triple: [British Southern strategy during the American Revolutionary War, instanceOf, British war plan]
-
A.
British military plan
chosen
A British military plan is a strategic and operational blueprint developed by the United Kingdom’s armed forces to achieve specific defense or combat objectives through coordinated use of personnel, equipment, and tactics.
-
B.
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.
-
C.
French military plan
A French military plan is a strategic and operational blueprint developed by France’s armed forces that outlines objectives, force deployment, and coordinated actions to achieve specific defense or combat goals.
-
D.
World War II directive
A World War II directive is an official, authoritative order or instruction issued by a military or governmental command during the Second World War to guide strategy, operations, or policy.
-
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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:49 p.m.