Triple
T1411848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Monetary Fund |
E31821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned regional monetary fund |
C7547
|
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: planned regional monetary fund Context triple: [African Monetary Fund, instanceOf, planned regional monetary fund]
-
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.
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.
-
C.
fiat currency
A fiat currency is a government-issued form of money that has value primarily because a government maintains it and people have faith in its acceptance, rather than being backed by a physical commodity like gold or silver.
-
D.
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.
-
E.
centralized economic planning system
A centralized economic planning system is a structure in which a central authority makes decisions about the allocation of resources, production targets, and distribution of goods and services across an economy.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.