Triple
T14436441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agentschap van het Rijk |
E357975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch public sector organization type |
C14101
|
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: Dutch public sector organization type Context triple: [Agentschap van het Rijk, instanceOf, Dutch public sector organization type]
-
A.
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.
-
B.
Dutch organization
A Dutch organization is an entity established in the Netherlands, operating under Dutch law to pursue specific economic, social, cultural, or governmental objectives.
-
C.
government body of the Kingdom of the Netherlands
chosen
A government body of the Kingdom of the Netherlands is an official public institution or authority, established by law, that exercises administrative, legislative, or judicial powers on behalf of the Dutch state or its constituent parts.
-
D.
Belgian federal public service
A Belgian federal public service is a national-level administrative body responsible for implementing federal government policies, delivering public services, and supporting the functioning of the Belgian state across its various domains of competence.
-
E.
Belgian public office
A Belgian public office is an official governmental body or administrative unit in Belgium responsible for implementing public policies, delivering services, and managing regulatory or administrative tasks within its jurisdiction.
- 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.