Triple
T7111248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omnibus Budget Reconciliation Act of 1990 |
E165710
|
entity |
| Predicate | budgetProcessImpact |
P8679
|
FINISHED |
| Object | strengthened PAYGO enforcement |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: strengthened PAYGO enforcement | Statement: [Omnibus Budget Reconciliation Act of 1990, budgetProcessImpact, strengthened PAYGO enforcement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetProcessImpact Context triple: [Omnibus Budget Reconciliation Act of 1990, budgetProcessImpact, strengthened PAYGO enforcement]
-
A.
budgetProcess
chosen
Indicates the relationship in which an entity is involved in, responsible for, or characterized by a specific budgeting or budget-planning process.
-
B.
budgetaryEffect
Indicates the financial impact or change in budget resulting from a particular action, decision, or policy.
-
C.
budgetScope
Indicates the extent or range of financial resources allocated or considered within a particular budget.
-
D.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
-
E.
budgetApproval
Indicates that a proposed budget has been formally reviewed and granted permission to be implemented or spent.
- F. None of above.
Provenance (3 batches)
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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.