Triple
T25930145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bipartisan Budget Act of 2018 |
E653415
|
entity |
| Predicate | setsBudgetAuthorityFor |
P159573
|
FINISHED |
| Object | fiscal year 2018 |
—
|
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: fiscal year 2018 | Statement: [Bipartisan Budget Act of 2018, setsBudgetAuthorityFor, fiscal year 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsBudgetAuthorityFor Context triple: [Bipartisan Budget Act of 2018, setsBudgetAuthorityFor, fiscal year 2018]
-
A.
setsBudgetFor
Indicates that one entity establishes or allocates a financial budget for another entity or activity.
-
B.
budgetaryAuthorityWith
Indicates that one entity has formal control or decision-making power over the allocation and use of another entity’s financial resources.
-
C.
hasBudgetaryAuthorityFrom
Indicates that one entity possesses formal power or permission, granted by another entity, to make or control budgetary or financial allocation decisions.
-
D.
budgetAuthority
Indicates that an entity has the formal power or authorization to allocate, commit, or control the use of financial resources for another entity or activity.
-
E.
authorizedBudget
Indicates that a specified budget amount has been formally approved for use by or for a particular entity or purpose.
- F. None of above. chosen
Provenance (4 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60418322081908411c24d1dc820de |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:36 a.m.