Triple
T13961012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutory Pay-As-You-Go Act of 2010 |
E335790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | budget enforcement law |
C18705
|
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 enforcement law Context triple: [Statutory Pay-As-You-Go Act of 2010, instanceOf, budget enforcement law]
-
A.
appropriations act
An appropriations act is a law passed by a legislature that authorizes specific government expenditures, allocating funds to agencies, programs, or activities for a defined period and purpose.
-
B.
budgetary framework
A budgetary framework is a structured system of rules, processes, and assumptions that guides how financial resources are planned, allocated, monitored, and controlled over a specific period.
-
C.
public finance legislation
chosen
Public finance legislation comprises the body of laws and regulations that govern how governments raise revenue, allocate expenditures, manage public debt, and oversee fiscal responsibility to achieve economic and social policy objectives.
-
D.
financial legislation
Financial legislation comprises the laws and regulations that govern the creation, management, oversight, and stability of financial systems, markets, institutions, and transactions.
-
E.
budget coordination function
A budget coordination function is a mechanism or process that aligns, integrates, and manages financial plans and resource allocations across different units or activities to ensure coherent and efficient use of funds.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.