Triple
T18731976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission Implementing Decision establishing the European Education and Culture Executive Agency |
E458055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Commission Implementing Decision |
C41548
|
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: Commission Implementing Decision Context triple: [Commission Implementing Decision establishing the European Education and Culture Executive Agency, instanceOf, Commission Implementing 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 decision
A Council decision is a formal, binding resolution adopted by a council body that determines a course of action, policy, or outcome on matters within its authority.
-
C.
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.
-
D.
decision instrument
A decision instrument is a structured tool or framework used to systematically evaluate options and guide the selection of an optimal course of action based on defined criteria.
-
E.
decree
A decree is an authoritative and formal order or decision issued by a person or body with legal or official power, often carrying the force of law.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:51 a.m.