Triple
T5938029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice-Chief of the Air Staff |
E132091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior Royal Air Force appointment |
C16500
|
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: senior Royal Air Force appointment Context triple: [Vice-Chief of the Air Staff, instanceOf, senior Royal Air Force appointment]
-
A.
Royal Air Force senior staff position
chosen
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.
-
B.
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.
-
C.
Chief of the Defence Staff of the United Kingdom
The Chief of the Defence Staff of the United Kingdom is the professional head of the British Armed Forces and the principal military adviser to the Secretary of State for Defence and the Prime Minister.
-
D.
major command of the Royal Air Force
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.
-
E.
military appointment
A military appointment is an official position or duty assigned to a service member within the armed forces, defining their role, responsibilities, and authority.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.