Triple
T20317038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Second Pension |
E510405
|
entity |
| Predicate | startTaxYear |
P79333
|
FINISHED |
| Object | 2002-2003 |
—
|
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: 2002-2003 | Statement: [State Second Pension, startTaxYear, 2002-2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTaxYear Context triple: [State Second Pension, startTaxYear, 2002-2003]
-
A.
startServiceYear
Indicates the year in which an entity began providing a particular service or started its service-related activity.
-
B.
introducedInTaxYear
chosen
Indicates that something (such as a rule, benefit, or provision) first became applicable or was brought into effect in a specified tax year.
-
C.
appliesToTaxYear
Indicates the specific tax year or fiscal period to which a tax-related rule, record, or obligation is applicable.
-
D.
financialYearStart
Indicates the date or point in time when an entity’s financial or fiscal year begins.
-
E.
startSeasonYear
Indicates the calendar year in which a particular season, series, or recurring event begins.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67788ca3c8190a3496fd54a5870d6 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.