Triple
T11274869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British expedition to Saint-Domingue |
E266908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military intervention |
C6026
|
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 military intervention Context triple: [British expedition to Saint-Domingue, instanceOf, British military intervention]
-
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.
military intervention
chosen
Military intervention is the deliberate use or deployment of a state's armed forces in another state's territory or conflict to influence political, security, or humanitarian outcomes.
-
C.
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.
-
D.
engagement of the Falklands War
The engagement of the Falklands War is a military operation or battle between British and Argentine forces during the 1982 conflict over the Falkland Islands, characterized by specific objectives, participating units, tactics, and outcomes within the broader campaign.
-
E.
British military administration
British military administration is the system of governance and organizational structures through which the British armed forces planned, directed, and controlled military operations and occupied territories.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.