Triple
T28169755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministerieel Comité voor de Inlichtingen- en Veiligheidsdiensten |
E715423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ministerieel comité |
C1999
|
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: ministerieel comité Context triple: [Ministerieel Comité voor de Inlichtingen- en Veiligheidsdiensten, instanceOf, ministerieel comité]
-
A.
government committee
chosen
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
B.
EU Council committee
An EU Council committee is a specialized working group composed of representatives from EU member states that prepares, negotiates, and coordinates issues and draft legislation for decision-making by the Council of the European Union.
-
C.
commissioner
A commissioner is an appointed or elected official responsible for overseeing, regulating, or managing a specific area of public administration, policy, or organizational activity.
-
D.
Joint committee of the Parliament of the United Kingdom
A Joint Committee of the Parliament of the United Kingdom is a committee composed of members from both the House of Commons and the House of Lords that examines specific issues, legislation, or matters of public importance.
-
E.
conference committee
A conference committee is a group of individuals responsible for planning, organizing, and overseeing the academic, logistical, and promotional aspects of a conference.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:12 p.m.