Triple
T29151333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Mobility Group RAAF |
E738916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RAAF group |
C24582
|
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: RAAF group Context triple: [Air Mobility Group RAAF, instanceOf, RAAF group]
-
A.
Royal Australian Air Force unit elements
chosen
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.
-
B.
Royal Australian Air Force unit
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.
-
C.
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.
-
D.
Commonwealth air force squadron
A Commonwealth air force squadron is a military aviation unit from a nation within the Commonwealth of Nations, typically comprising aircraft, aircrew, and support personnel organized for operational, training, or support missions under a unified command structure.
-
E.
branch of the Royal Australian Air Force
A branch of the Royal Australian Air Force is a major organizational subdivision responsible for specific operational, support, or administrative functions within the RAAF’s overall air power mission.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:42 a.m.