Triple
T4949699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Impact |
E111138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian military operation |
C340
|
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: Canadian military operation Context triple: [Operation Impact, instanceOf, Canadian military operation]
-
A.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
B.
Canadian Armed Forces sub-component
A Canadian Armed Forces sub-component is a distinct organizational element within the Canadian military structure, such as a specific command, formation, or unit, that performs defined roles and responsibilities in support of national defense objectives.
-
C.
Canadian Expeditionary Force formation
A Canadian Expeditionary Force formation is an organized military unit or grouping, such as a battalion, brigade, or division, raised by Canada for overseas service during the First World War.
-
D.
military intervention
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.
-
E.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.