Triple
T8648274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Williams |
E205033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Air Force officer |
C24807
|
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 officer Context triple: [Richard Williams, instanceOf, Royal Australian Air Force officer]
-
A.
Chief of the Air Staff of the Royal Air Force
The Chief of the Air Staff of the Royal Air Force is the professional head and highest-ranking officer of the RAF, responsible for its overall command, operational readiness, and strategic direction.
-
B.
Royal Air Force senior staff position
A Royal Air Force senior staff position is a high-ranking leadership role responsible for directing major operational, strategic, or administrative functions within the RAF’s command structure.
-
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.
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.
-
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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.