Triple
T8628840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 295 Squadron RAAF |
E204347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Air Force squadron |
C24415
|
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 Australian Air Force squadron Context triple: [No. 295 Squadron RAAF, instanceOf, Royal Australian Air Force squadron]
-
A.
Royal Australian Air Force unit
chosen
A Royal Australian Air Force unit is an organizational entity within the RAAF, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support roles in air and space power.
-
B.
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.
-
C.
Royal Australian Air Force unit elements
Royal Australian Air Force unit elements are the organizational components—such as squadrons, wings, and support units—that structure, operate, and sustain the RAAF’s air power capabilities.
-
D.
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.
-
E.
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.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.