Triple
T27930961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Board of the Defence Council |
E707978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence governance body |
C172
|
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: defence governance body Context triple: [Air Force Board of the Defence Council, instanceOf, defence governance body]
-
A.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
governance entity
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
-
C.
defence establishment
A defence establishment is an organized institution or network of institutions responsible for planning, maintaining, and deploying a nation's military capabilities and security infrastructure.
-
D.
defense acquisition governance body
A defense acquisition governance body is an authoritative organization or board that oversees, directs, and approves major decisions, resources, and policies throughout the defense acquisition lifecycle to ensure alignment with strategic, legal, and budgetary requirements.
-
E.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:03 p.m.