Triple
T5532952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Force (Royal Canadian Air Force) |
E145092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air force component |
C2925
|
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: air force component Context triple: [Regular Force (Royal Canadian Air Force), instanceOf, air force component]
-
A.
air force wing
An air force wing is a major operational unit composed of multiple squadrons and support elements, organized to conduct and sustain specific air missions under a unified command.
-
B.
Tactical air force
A tactical air force is a military aviation organization focused on providing direct air support, interdiction, and battlefield air operations in coordination with ground and naval forces within a specific theater of operations.
-
C.
aerial warfare service branch
chosen
An aerial warfare service branch is a military organization responsible for conducting and supporting combat and operational activities in the air and, increasingly, in space and cyberspace domains.
-
D.
airborne corps
An airborne corps is a large military formation composed primarily of paratrooper and air-transportable units, organized and equipped to conduct large-scale airborne operations behind or across enemy lines.
-
E.
United States Air Force organization
A United States Air Force organization is a structured unit or entity within the Air Force, such as a squadron, group, wing, or command, established to perform specific operational, support, or administrative missions in support of national defense objectives.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:34 p.m.