Triple
T4834514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) No 1092/2010 |
E108024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU financial regulation |
C14089
|
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 financial regulation Context triple: [Regulation (EU) No 1092/2010, instanceOf, EU financial regulation]
-
A.
European Union regulation
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.
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.
-
C.
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.
-
D.
EU legal act
chosen
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.
-
E.
financial reform
Financial reform is the process of redesigning laws, regulations, and institutions in the financial system to improve stability, fairness, transparency, and economic efficiency.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:25 p.m.