Triple
T31971544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Commander Australia |
E816325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Air Force position |
C32377
|
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 position Context triple: [Air Commander Australia, instanceOf, Royal Australian Air Force position]
-
A.
Royal Australian Air Force officer
A Royal Australian Air Force officer is a commissioned member of Australia's air and space warfare branch responsible for leading personnel, managing operations, and upholding the defense and strategic interests of the nation.
-
B.
Royal Australian Air Force personnel
chosen
Individuals who serve or have served in the Royal Australian Air Force, fulfilling military, technical, and support roles in Australia's air and space defense forces.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:10 a.m.