Triple
T27027814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida House Appropriations Committee |
E680835
|
entity |
| Predicate | typeOfBudgetHandled |
P2120
|
FINISHED |
| Object | operating budget |
—
|
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: operating budget | Statement: [Florida House Appropriations Committee, typeOfBudgetHandled, operating budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBudgetHandled Context triple: [Florida House Appropriations Committee, typeOfBudgetHandled, operating budget]
-
A.
typeOfBudgetRole
Indicates that one entity functions as a specific budget-related role or responsibility type in relation to another entity.
-
B.
budgetType
chosen
Indicates the classification or category of a budget associated with an entity or financial activity.
-
C.
budgetTypeManaged
Indicates that the budget is controlled or administered under a specific management scheme or authority.
-
D.
budgetingSystem
Indicates a system or process used to plan, allocate, track, and control financial resources or budgets.
-
E.
hasBudgetFor
Indicates that an entity possesses sufficient allocated financial resources to support, fund, or carry out another specified entity, activity, or purpose.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 27, 2026, 7:12 a.m.