Triple
T32688478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | budget reconciliation act |
E835791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | budget reconciliation bill |
C32957
|
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 reconciliation bill Context triple: [budget reconciliation act, instanceOf, budget reconciliation bill]
-
A.
United States federal budget reconciliation legislation series
chosen
A United States federal budget reconciliation legislation series is a sequence of budget-related laws passed through the expedited reconciliation process, allowing certain fiscal measures to be enacted with limited debate and a simple majority in the Senate.
-
B.
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.
-
C.
money bill
A money bill is a physical or digital document that represents a specific monetary value and is used as a medium of exchange in financial transactions.
-
D.
budgetary committee
A budgetary committee is a group responsible for planning, reviewing, and overseeing an organization’s financial allocations and expenditures to ensure resources are used effectively and align with strategic goals.
-
E.
joint resolution of the United States Congress
A joint resolution of the United States Congress is a legislative measure requiring approval by both the House and Senate and, in most cases, the President’s signature, often used for specific purposes such as constitutional amendments, continuing appropriations, or limited policy actions.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:09 a.m.