Triple
T3769484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERM |
E82761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European monetary system component |
C14094
|
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 monetary system component Context triple: [ERM, instanceOf, European monetary system component]
-
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.
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.
-
C.
proposed supranational currency unit
A proposed supranational currency unit is a theoretical monetary unit designed to function as a common medium of exchange and store of value across multiple sovereign nations, operating above and alongside their national currencies.
-
D.
planned regional monetary fund
A planned regional monetary fund is a proposed financial institution designed to pool resources from member countries within a specific region to provide monetary stability, balance-of-payments support, and coordinated economic policies.
-
E.
European Union body
A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.