Triple
T2913866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Management and Budget liaison functions |
E63750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | budget coordination function |
C11865
|
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: budget coordination function Context triple: [Office of Management and Budget liaison functions, instanceOf, budget coordination function]
-
A.
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.
-
B.
government budget
A government budget is a financial plan that outlines a government's projected revenues and expenditures over a specific period, typically one fiscal year, to achieve its economic and policy objectives.
-
C.
budgetary policy announcement
A budgetary policy announcement is an official communication by a government or authority outlining planned public revenues, expenditures, and fiscal measures for a specific period.
-
D.
fiscal policy program
A fiscal policy program is a coordinated set of government actions and rules that use taxation, spending, and borrowing to influence economic activity, growth, and stability.
-
E.
labour market coordination mechanism
A labour market coordination mechanism is the set of institutions, rules, and practices through which employers, workers, and the state align wage-setting, employment conditions, and labour allocation across the economy.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:11 p.m.