Triple
T27976548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Armed Forces strategic level commands |
E706505
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military command structure element |
C37128
|
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: military command structure element Context triple: [Canadian Armed Forces strategic level commands, instanceOf, military command structure element]
-
A.
military structure
A military structure is an organized framework of ranks, units, and command relationships that defines how armed forces are arranged, governed, and coordinated to conduct operations.
-
B.
military administrative structure
A military administrative structure is the organized system of offices, roles, procedures, and chains of command that manage the planning, support, and governance of armed forces.
-
C.
command and control structure
chosen
A command and control structure is an organizational framework that defines how authority, decision-making, and information flow are coordinated to direct and manage operations toward specific objectives.
-
D.
naval command structure
A naval command structure is the hierarchical organization of authority, responsibility, and communication within a navy that directs the planning, coordination, and execution of maritime operations.
-
E.
component of NATO command structure
A component of NATO command structure is an organizational entity—such as a headquarters, command, or specialized unit—responsible for planning, directing, and coordinating specific military or strategic functions within the Alliance’s integrated chain of command.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:41 p.m.