Triple
T5405324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15 Wing Moose Jaw |
E120878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Canadian Air Force wing |
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 wing Context triple: [15 Wing Moose Jaw, instanceOf, Royal Canadian Air Force wing]
-
A.
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.
-
B.
Royal Air Force squadron
A Royal Air Force squadron is a military aviation unit comprising aircraft, aircrew, and support personnel organized under a specific command structure to perform designated operational, training, or support roles.
-
C.
Royal Air Force Regiment squadron
A Royal Air Force Regiment squadron is a specialized ground combat and force protection unit of the RAF responsible for defending airfields, aircraft, and related assets through infantry, air defense, and security operations.
-
D.
branch of the Royal Air Force
A branch of the Royal Air Force is a major organizational subdivision responsible for a specific functional area of air and space operations, support, or administration within the RAF.
-
E.
Australian Flying Corps squadron
An Australian Flying Corps squadron is a military aviation unit from Australia’s early air arm, typically composed of pilots, aircraft, and support personnel organized to conduct reconnaissance, combat, and support missions during World War I.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:05 p.m.