Triple
T23777794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budget Implementation Act, 2018, No. 1 |
E587722
|
entity |
| Predicate | yearOfBudget |
P8230
|
FINISHED |
| Object | 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: 2018 | Statement: [Budget Implementation Act, 2018, No. 1, yearOfBudget, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfBudget Context triple: [Budget Implementation Act, 2018, No. 1, yearOfBudget, 2018]
-
A.
budgetFiscalYear
chosen
Indicates the fiscal year to which a particular budget or budgeting activity applies.
-
B.
budgetaryYearAlignment
Indicates that two or more entities have fiscal or budgetary years that coincide or are structured to match each other in timing and duration.
-
C.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
D.
hasCapitalBudgetFor
Indicates that an entity allocates or designates financial resources specifically for capital expenditures related to another entity or purpose.
-
E.
lastSeparateBudgetYear
Indicates the most recent year in which the entities maintained or operated under separate budgets rather than a combined one.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46d55588190ad9c7e3c729b6b17 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.