Triple
T9575413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SELIC rate |
E231032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monetary policy instrument |
C15638
|
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 policy instrument Context triple: [SELIC rate, instanceOf, monetary policy instrument]
-
A.
fiscal policy instrument
A fiscal policy instrument is a tool used by a government—such as taxation, public spending, or subsidies—to influence economic activity, stabilize the economy, and achieve policy objectives.
-
B.
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.
-
C.
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.
-
D.
monetary policy interest rate
chosen
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.
-
E.
economic policy coordination tool
An economic policy coordination tool is a system that helps governments and institutions design, align, and monitor fiscal, monetary, and regulatory policies to achieve shared macroeconomic objectives.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:05 p.m.