Triple
T5314427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New State Pension |
E119111
|
entity |
| Predicate | isIndividualBenefit |
P63439
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [New State Pension, isIndividualBenefit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndividualBenefit Context triple: [New State Pension, isIndividualBenefit, true]
-
A.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
benefitAdministered
Indicates that a benefit (such as aid, service, or entitlement) has been formally provided or delivered to an eligible recipient by an administering party.
-
C.
benefitForm
Indicates that one entity is a specific form, type, or variant in which a benefit is provided or realized for another entity.
-
D.
benefitProgramInvolved
Indicates that a benefit program participates in, is associated with, or plays a role in the referenced situation or relationship.
-
E.
exclusiveBenefit
Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
- F. None of above. chosen
Provenance (4 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd86f0cbfc8190b6665dd9b28d6345 |
completed | March 20, 2026, 5:42 p.m. |
Created at: March 20, 2026, 1:54 p.m.