Triple
T38411036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministerie van Buitenlandse Zaken |
E901474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | onderdeel van de Rijksoverheid |
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: onderdeel van de Rijksoverheid Context triple: [Ministerie van Buitenlandse Zaken, instanceOf, onderdeel van de Rijksoverheid]
-
A.
governmental department
A governmental department is an official administrative division of a government responsible for managing specific public policies, services, or functions within its designated area of authority.
-
B.
departmental government
A departmental government is a form of executive organization in which authority is divided among specialized departments, each headed by a minister or secretary responsible for a specific policy area.
-
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.
department of a ministry
A department of a ministry is an organizational unit within a government ministry responsible for managing specific policy areas, programs, or administrative functions under the ministry’s overall mandate.
-
E.
branch of government
A branch of government is a major division of a state's governing system, such as the executive, legislative, or judicial branch, each with distinct powers and responsibilities designed to balance and limit authority.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.