Triple
T33513734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMCO |
E858311
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Union 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: European Union advisory committee Context triple: [EMCO, instanceOf, European Union advisory committee]
-
A.
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.
-
B.
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.
-
C.
European Union Council Decision
A European Union Council Decision is a binding legal act adopted by the Council of the EU that addresses specific cases or recipients, such as particular member states or individuals, and is directly applicable to them.
-
D.
European Union convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
E.
European organisation
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.