Triple
T25782422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldrich Plan |
E649325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monetary reform plan |
C48927
|
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 reform plan Context triple: [Aldrich Plan, instanceOf, monetary reform plan]
-
A.
historical monetary reform process
chosen
A historical monetary reform process is a coordinated set of policy decisions and institutional changes implemented at a specific time and place to alter a society’s currency system, money supply mechanisms, or monetary standards in response to economic, political, or social conditions.
-
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.
proposed currency
A proposed currency is a conceptual monetary unit or system that has been designed and suggested for adoption but is not yet officially issued, regulated, or widely used in economic transactions.
-
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.
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.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:51 a.m.