Triple
T4317314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU, Euratom) No 1141/2014 |
E96424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU regulation |
C6352
|
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 regulation Context triple: [Regulation (EU, Euratom) No 1141/2014, instanceOf, EU regulation]
-
A.
European Union regulation
chosen
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
-
B.
EU legal act
An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
-
C.
European Union policy framework
The European Union policy framework is the overarching system of treaties, institutions, laws, and coordinated strategies through which EU member states collectively design, implement, and enforce policies across economic, social, environmental, and security domains.
-
D.
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.
-
E.
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.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:12 p.m.