Triple
T29072538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundell assignment rule |
E735847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | macroeconomic policy rule |
C21850
|
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: macroeconomic policy rule Context triple: [Mundell assignment rule, instanceOf, macroeconomic policy rule]
-
A.
monetary policy framework
chosen
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.
macroeconomic principle
A macroeconomic principle is a fundamental concept or rule that explains the behavior and interactions of an economy as a whole, including aggregate output, inflation, unemployment, and growth.
-
C.
macroeconomic theory
Macroeconomic theory is the branch of economics that studies the behavior, performance, and structure of an economy as a whole, focusing on aggregate measures like output, inflation, unemployment, and economic growth, and the policies that influence them.
-
D.
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.
-
E.
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.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:20 a.m.