Triple
T8609765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANEP |
E203887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous public body |
C1300
|
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: autonomous public body Context triple: [ANEP, instanceOf, autonomous public body]
-
A.
non-departmental public body
A non-departmental public body is an organization that operates at arm’s length from government departments to carry out public functions, often with its own board and a degree of operational independence while remaining publicly accountable.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
independent administrative authority
chosen
An independent administrative authority is a public body, separate from the traditional executive hierarchy, endowed with regulatory or supervisory powers and functional autonomy to ensure impartial decision-making in a specific sector or policy area.
-
D.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
-
E.
governing body
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.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:25 p.m.