Triple
T28267486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QPP |
E712743
|
entity |
| Predicate | benefitsBasedOn |
P167766
|
FINISHED |
| Object | contributory earnings record |
—
|
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: contributory earnings record | Statement: [QPP, benefitsBasedOn, contributory earnings record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitsBasedOn Context triple: [QPP, benefitsBasedOn, contributory earnings record]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
benefitLevelBasedOn
chosen
Indicates that the degree or amount of benefit is determined according to a specified basis, condition, or criterion.
-
C.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
D.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
E.
criterionForBenefits
Indicates that something serves as a condition or standard that must be met in order for an entity to receive certain benefits.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 11:15 p.m.