Triple
T21879394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2 Canadian Air Division |
E540237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Canadian Air Force formation |
C6694
|
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: Royal Canadian Air Force formation Context triple: [2 Canadian Air Division, instanceOf, Royal Canadian Air Force formation]
-
A.
Royal Australian Air Force formation
A Royal Australian Air Force formation is an organizational grouping of RAAF units, aircraft, and personnel structured to conduct specific operational, training, or support roles under a unified command.
-
B.
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.
-
C.
component of the Royal Canadian Air Force
chosen
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.
-
D.
Royal Canadian Air Force base
A Royal Canadian Air Force base is a military installation operated by the Royal Canadian Air Force that supports air operations, training, maintenance, and administration for Canada’s air defence and aerospace missions.
-
E.
Royal Australian Air Force wing
A Royal Australian Air Force wing is a major operational or support formation comprising multiple squadrons and units, responsible for coordinating and delivering specific air power capabilities within the RAAF.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:04 p.m.