Triple
T17349112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Australian Air Force medical services |
E421759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Royal Australian Air Force |
C38448
|
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: branch of the Royal Australian Air Force Context triple: [Royal Australian Air Force medical services, instanceOf, branch of the Royal Australian Air Force]
-
A.
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.
-
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.
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.
-
D.
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.
-
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. chosen
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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.