Triple
T5329291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Monetary Cooperation Fund |
E123263
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monetary cooperation mechanism |
C2063
|
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 cooperation mechanism Context triple: [European Monetary Cooperation Fund, instanceOf, monetary cooperation mechanism]
-
A.
monetary system
A monetary system is the structured framework of institutions, rules, instruments, and practices a society uses to create, manage, and exchange money as a medium of value.
-
B.
economic policy coordination tool
An economic policy coordination tool is a system that helps governments and institutions design, align, and monitor fiscal, monetary, and regulatory policies to achieve shared macroeconomic objectives.
-
C.
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.
-
D.
international cooperation mechanism
chosen
An international cooperation mechanism is a structured framework, agreement, or institution through which multiple countries coordinate policies, share resources, and jointly address cross-border issues or common goals.
-
E.
international monetary system
The international monetary system is the set of rules, institutions, and arrangements that govern how countries manage exchange rates, conduct cross-border payments, and coordinate their monetary and financial relations.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2 p.m.