Triple
T14786177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Expeditionary Force Command |
E347530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Forces formation |
C14213
|
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 Forces formation Context triple: [Canadian Expeditionary Force Command, instanceOf, Canadian Forces formation]
-
A.
Royal Canadian Navy formation
A Royal Canadian Navy formation is an organized operational grouping of naval units, personnel, and resources structured under a unified command to conduct maritime missions and support national defense objectives.
-
B.
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.
-
C.
Canadian Armed Forces sub-component
chosen
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.
-
D.
Canadian military institution
A Canadian military institution is an organization established by the Government of Canada to develop, manage, and support the nation’s armed forces through training, policy, operations, and defense-related services.
-
E.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.