Triple
T3674161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Home Commands |
E77949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force command structure |
C6954
|
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 Air Force command structure Context triple: [RAF Home Commands, instanceOf, Royal Air Force command structure]
-
A.
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.
-
B.
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.
-
C.
major command of the Royal Air Force
chosen
A major command of the Royal Air Force is a high-level organizational formation responsible for directing and coordinating air operations, support, and resources within a defined functional or geographic area.
-
D.
Allied air force
Allied air force: The collective aerial military forces of nations united in a coalition, coordinating air operations to achieve shared strategic and tactical objectives in conflict.
-
E.
organisational unit of the UK Ministry of Defence
An organisational unit of the UK Ministry of Defence is a formally defined structural entity within the department, such as a command, agency, directorate, or division, responsible for specific defence-related functions, resources, and decision-making.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.