Triple
T6780672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bijeenkomst voor Federaal Overleg |
E155672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal consultation body |
C655
|
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: federal consultation body Context triple: [Bijeenkomst voor Federaal Overleg, instanceOf, federal consultation body]
-
A.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
B.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
C.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
D.
Canadian federal commission
A Canadian federal commission is an independent or semi-independent body established by the Government of Canada to investigate, regulate, or provide expert advice on specific national issues or policy areas.
-
E.
ad hoc governmental body
An ad hoc governmental body is a temporary, specially formed public entity created by a government to address a specific issue, task, or crisis and dissolved once its purpose is fulfilled.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.