Triple
T4466843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Council functions within Ministry of Defence |
E98399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governmental function |
C11864
|
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: governmental function Context triple: [Air Council functions within Ministry of Defence, instanceOf, governmental function]
-
A.
administrative function
chosen
An administrative function is a conceptual class representing tasks and processes that support the organization, coordination, and control of operations within an institution or system.
-
B.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
C.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
D.
governmental procedure
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
-
E.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:34 p.m.