Triple
T11865054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010–2012 UK Parliament |
E282258
|
entity |
| Predicate | fiscalPolicy |
P68205
|
FINISHED |
| Object | austerity programme |
—
|
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: austerity programme | Statement: [2010–2012 UK Parliament, fiscalPolicy, austerity programme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalPolicy Context triple: [2010–2012 UK Parliament, fiscalPolicy, austerity programme]
-
A.
fiscalPolicyType
chosen
Indicates the specific category or approach of a government’s fiscal policy applied in a given context.
-
B.
economicPolicyTools
Indicates the relationship in which specific instruments or measures are used to implement or influence a government's or institution's economic policy.
-
C.
fiscalIssue
Indicates a relationship where an entity is involved in, affected by, or associated with a financial or budgetary problem, concern, or matter.
-
D.
economicPolicyType
Indicates the classification of an economic policy according to its general type or category (e.g., fiscal, monetary, trade).
-
E.
economicPolicyOutcome
Indicates the resulting economic conditions, effects, or consequences that arise from implementing a particular economic policy.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.