Triple
T21780787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve reserve requirement increases of 1936–1937 |
E537705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monetary tightening episode |
C45277
|
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 tightening episode Context triple: [Federal Reserve reserve requirement increases of 1936–1937, instanceOf, monetary tightening episode]
-
A.
disinflationary policy episode
A disinflationary policy episode is a period during which authorities deliberately implement monetary and/or fiscal measures to reduce the rate of inflation, typically at the cost of short-term output or employment losses.
-
B.
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.
-
C.
monetary policy interest rate
The monetary policy interest rate is the benchmark rate set by a central bank to influence borrowing costs, economic activity, and inflation in an economy.
-
D.
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.
-
E.
economic policy meeting
An economic policy meeting is a formal gathering where policymakers, experts, and stakeholders discuss, evaluate, and decide on strategies and measures to influence a region’s or nation’s economic performance.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:52 p.m.