Triple
T21780786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve reserve requirement increases of 1936–1937 |
E537705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reserve requirement change |
C3763
|
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: reserve requirement change Context triple: [Federal Reserve reserve requirement increases of 1936–1937, instanceOf, reserve requirement change]
-
A.
reserve currency
A reserve currency is a widely trusted national currency that governments and institutions hold in large quantities for international trade, financial stability, and backing their own domestic currencies.
-
B.
interest rate rule
An interest rate rule is a systematic policy guideline that prescribes how a central bank should adjust its policy interest rate in response to changes in economic conditions such as inflation and output.
-
C.
consensus rule change
A consensus rule change is a modification to the fundamental validation rules that all nodes in a distributed system or blockchain must follow to agree on the state of the ledger.
-
D.
financial reform
chosen
Financial reform is the process of redesigning laws, regulations, and institutions in the financial system to improve stability, fairness, transparency, and economic efficiency.
-
E.
bail-in provision
A bail-in provision is a contractual or statutory mechanism that allows a failing financial institution’s creditors and, in some cases, shareholders to have their claims written down or converted into equity to recapitalize the institution and avoid taxpayer-funded bailouts.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:52 p.m.