Triple
T244805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of California |
E5012
|
entity |
| Predicate | budgetProcess |
P8679
|
FINISHED |
| Object | annual state 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: annual state budget | Statement: [Government of California, budgetProcess, annual state budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetProcess Context triple: [Government of California, budgetProcess, annual state budget]
-
A.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
-
B.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
C.
budgetFunction
Indicates a relationship where a specific budgeting rule or formula determines how resources or funds are allocated or constrained for an entity or activity.
-
D.
budgetUnit
Indicates that one entity functions as the budgetary unit or cost-accounting unit associated with another entity within a financial or organizational context.
-
E.
budgetSource
Indicates the origin or provider of the funds used to finance a particular activity, project, or expenditure.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.