Triple
T5314428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New State Pension |
E119111
|
entity |
| Predicate | isBasedOnPartnerContributions |
P1136
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [New State Pension, isBasedOnPartnerContributions, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBasedOnPartnerContributions Context triple: [New State Pension, isBasedOnPartnerContributions, false]
-
A.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
B.
hasPartner
chosen
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
C.
contributionBase
Indicates the foundational amount, value, or resource on which a contribution, payment, or benefit is calculated or determined.
-
D.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
-
E.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
- 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_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. |
Created at: March 20, 2026, 1:54 p.m.