Triple
T29577183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Decision (CFSP) 2015/778 |
E753474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Union Council Decision |
C55918
|
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 Council Decision Context triple: [Council Decision (CFSP) 2015/778, instanceOf, European Union Council Decision]
-
A.
European Council decision
A European Council decision is a binding legal act adopted by the European Council that sets specific rules, measures, or positions for particular situations or addressees within the European Union’s institutional framework.
-
B.
Council conclusions of the European Union
Council conclusions of the European Union are formal, non-legally binding statements adopted by the Council that express the EU member states’ collective political positions, priorities, or intended actions on specific policy issues.
-
C.
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.
-
D.
European Union position
A European Union position is an official, collectively agreed stance or policy adopted by EU institutions or member states on a specific issue, guiding the Union’s actions and negotiations internally and externally.
-
E.
Commission Implementing Decision
A Commission Implementing Decision is a legally binding act adopted by the European Commission to ensure uniform conditions for implementing EU legislation across all Member States.
- F. None of above. chosen
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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:04 p.m.