Triple
T27976641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Armed Forces strategic leadership |
E706507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic command function |
C47034
|
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: strategic command function Context triple: [Canadian Armed Forces strategic leadership, instanceOf, strategic command function]
-
A.
military operational function
A military operational function is a fundamental category of related tasks and capabilities that collectively enable armed forces to plan, conduct, and sustain operations to achieve strategic and tactical objectives.
-
B.
military advisory command
A military advisory command is an organizational unit responsible for providing strategic, operational, and technical guidance to allied or subordinate forces to enhance their effectiveness and interoperability.
-
C.
command and control structure
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.
command and control activity
chosen
A command and control activity is an operation or process through which authority is exercised to direct, coordinate, and manage resources and actions toward achieving specific objectives.
-
E.
major command echelon
A major command echelon is a high-level organizational tier within a military or large institution that oversees multiple subordinate units and directs strategic operations, resources, and policies across a broad mission area.
- 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.