Triple
T16172119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of European Banking Supervisors |
E392465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU advisory 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: EU advisory body Context triple: [Committee of European Banking Supervisors, instanceOf, EU advisory body]
-
A.
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.
-
B.
UK–EU body
A UK–EU body is a joint institutional entity established by agreements between the United Kingdom and the European Union to oversee, implement, or manage specific aspects of their bilateral relationship.
-
C.
European Union body
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.
-
D.
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.
-
E.
OECD body
An OECD body is an organizational entity within the Organisation for Economic Co-operation and Development that carries out specific functions such as policy development, coordination, analysis, or decision-making among member countries.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.