Triple
T29966852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rules versus Authorities in Monetary Policy |
E761207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | work on monetary policy |
C56594
|
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: work on monetary policy Context triple: [Rules versus Authorities in Monetary Policy, instanceOf, work on monetary policy]
-
A.
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.
-
B.
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.
-
C.
monetary policy region
A monetary policy region is a geographic or economic area within which a single monetary authority implements a unified set of monetary policy tools and rules, typically sharing a common currency and interest rate framework.
-
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.
Federal Reserve policy tool
A Federal Reserve policy tool is a mechanism—such as setting interest rates, adjusting reserve requirements, or conducting open market operations—that the Federal Reserve uses to influence money supply, credit conditions, and overall economic activity.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:30 p.m.