Triple
T1710984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of the Regions |
E36981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU advisory committee |
C2118
|
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: EU advisory committee Context triple: [Committee of the Regions, instanceOf, EU advisory committee]
-
A.
advisory body
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.
-
B.
international expert committee
An international expert committee is a formally organized group of specialists from multiple countries who collaboratively provide authoritative analysis, guidance, and recommendations on complex global issues within a specific domain.
-
C.
government committee
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.
-
D.
scientific committee
A scientific committee is a group of experts who collaboratively evaluate, guide, and make decisions on scientific matters, such as research quality, funding, ethics, and strategic priorities.
-
E.
European Union body
chosen
A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.