Triple
T15932026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Regulation (EU) No 1024/2013 |
E386345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU banking union legislation |
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 banking union legislation Context triple: [Council Regulation (EU) No 1024/2013, instanceOf, EU banking union legislation]
-
A.
economic and monetary union
An economic and monetary union is an integration arrangement in which participating countries coordinate economic policies, remove barriers to trade and capital movement, and adopt a common currency managed by a shared central monetary authority.
-
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 Central Bank document
A European Central Bank document is an official written record produced or endorsed by the ECB that communicates its policies, decisions, analyses, regulations, or operational information related to the euro area’s monetary and financial system.
-
D.
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.
-
E.
currency union
A currency union is an agreement between two or more countries to share a common currency and monetary policy, typically managed by a joint central authority.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.