Triple
T38083519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Pension |
E950915
|
entity |
| Predicate | statePensionAge |
P32720
|
FINISHED |
| Object | varies by date of birth |
—
|
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: varies by date of birth | Statement: [State Pension, statePensionAge, varies by date of birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statePensionAge Context triple: [State Pension, statePensionAge, varies by date of birth]
-
A.
pensionEligibility
Indicates that an entity qualifies to receive pension benefits under specified rules or conditions.
-
B.
latestRetirementPensionStartAge
Indicates the most recent or maximum age at which an individual’s retirement pension payments are scheduled to begin.
-
C.
retirementPensionNormalStartAge
chosen
Indicates the standard or default age at which an individual becomes eligible to begin receiving their retirement pension benefits.
-
D.
earliestRetirementPensionStartAge
Indicates the minimum age at which an individual is first allowed to begin receiving retirement pension benefits.
-
E.
mandatoryRetirementAge
Indicates the age at which an individual is required by rule or policy to retire from a position or role.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 3, 2026, 4:21 p.m.