Triple
T14436322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministerie van Binnenlandse Zaken en Koninkrijksrelaties |
E357972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | overheidsorganisatie |
C3952
|
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: overheidsorganisatie Context triple: [Ministerie van Binnenlandse Zaken en Koninkrijksrelaties, instanceOf, overheidsorganisatie]
-
A.
governmental organization
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Dutch public body
A Dutch public body is an organization established by or under Dutch public law, entrusted with performing public tasks or exercising public authority under government oversight.
-
E.
government-backed organization
A government-backed organization is an entity that operates with financial support, authorization, or guarantees from a government to carry out specific public, economic, or policy-related functions.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.