Triple
T28484818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First May ministry |
E720798
|
entity |
| Predicate | budgetaryPeriodWithin |
P4343
|
FINISHED |
| Object | 2016–17 United Kingdom budget |
—
|
NE NERFINISHED |
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: 2016–17 United Kingdom budget | Statement: [First May ministry, budgetaryPeriodWithin, 2016–17 United Kingdom budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetaryPeriodWithin Context triple: [First May ministry, budgetaryPeriodWithin, 2016–17 United Kingdom budget]
-
A.
budgetFiscalYear
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.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
D.
fundingPeriod
Indicates the time span or duration for which funding is allocated, active, or valid within a financial or grant-related relationship.
-
E.
budgetScope
Indicates the extent or range of financial resources allocated or considered within a particular budget.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 2:57 a.m.