Triple
T27930962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Board of the Defence Council |
E707978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air force governing body |
C53555
|
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: air force governing body Context triple: [Air Force Board of the Defence Council, instanceOf, air force governing body]
-
A.
Air Force organization
An Air Force organization is a structured unit within an air force responsible for planning, directing, and executing air and space operations, support, or administration to achieve military objectives.
-
B.
United States Air Force organization
A United States Air Force organization is a structured unit or entity within the Air Force, such as a squadron, group, wing, or command, established to perform specific operational, support, or administrative missions in support of national defense objectives.
-
C.
military aviation command
A military aviation command is an organizational unit responsible for planning, directing, coordinating, and controlling the employment, readiness, and support of air forces to achieve strategic and operational military objectives.
-
D.
air force commander
An air force commander is a senior military officer responsible for planning, directing, and overseeing air operations, personnel, and resources to achieve strategic and tactical objectives.
-
E.
air force wing
An air force wing is a major operational unit composed of multiple squadrons and support elements, organized to conduct and sustain specific air missions 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:03 p.m.