Triple
T28153881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COATS |
E714691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Armed Forces component |
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 Armed Forces component Context triple: [COATS, instanceOf, Canadian Armed Forces component]
-
A.
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.
-
B.
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.
-
C.
Canadian militia infantry regiment
A Canadian militia infantry regiment is a part-time, citizen-soldier military unit organized to provide trained infantry forces for national defense, domestic operations, and support to the regular Canadian Army.
-
D.
Canadian Armed Forces position
A Canadian Armed Forces position is a defined role within Canada's military organization that specifies an individual's rank, duties, responsibilities, and placement within the command structure.
-
E.
component of the Royal Canadian Air Force
A component of the Royal Canadian Air Force is an organizational subdivision, such as a command, wing, squadron, or unit, that performs specific operational, support, or administrative functions within the RCAF structure.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:01 p.m.