Triple
T14384166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesbank Executive Board members |
E356680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monetary policy decision-makers |
C15750
|
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 decision-makers Context triple: [Bundesbank Executive Board members, instanceOf, monetary policy decision-makers]
-
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.
economic policy committee
An economic policy committee is a group of experts and stakeholders tasked with analyzing economic conditions and recommending or deciding on policies to guide a nation’s or organization’s economic strategy.
-
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.
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.
-
E.
central bank committee
chosen
A central bank committee is a decision-making body within a central bank responsible for setting and overseeing monetary policy, such as interest rates and liquidity measures, to achieve macroeconomic objectives like price stability and sustainable growth.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.