Triple
T21769730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAC Treaty and EAMU Protocol |
E537391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monetary union legal framework |
C214
|
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: monetary union legal framework Context triple: [EAC Treaty and EAMU Protocol, instanceOf, monetary union legal framework]
-
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.
European Union financial stability mechanism
The European Union financial stability mechanism is a framework of instruments and institutions designed to prevent, manage, and resolve financial crises within EU member states by providing conditional financial assistance and safeguarding the stability of the euro area and the broader EU economy.
-
D.
monetary policy framework
A monetary policy framework is the structured set of principles, rules, tools, and institutional arrangements that guide a central bank’s decisions to achieve macroeconomic objectives such as price stability, full employment, and financial stability.
-
E.
monetary law
chosen
Monetary law is the body of legal rules and principles governing the creation, issuance, regulation, and use of money and currency within and across jurisdictions.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.