Triple

T13889453
Position Surface form Disambiguated ID Type / Status
Subject BPS-1 E333930 entity
Predicate pensionEligibility P111888 FINISHED
Object eligible under government rules (if permanent) 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: eligible under government rules (if permanent) | Statement: [BPS-1, pensionEligibility, eligible under government rules (if permanent)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pensionEligibility
Context triple: [BPS-1, pensionEligibility, eligible under government rules (if permanent)]
  • A. mandatoryRetirementAge
    Indicates the age at which an individual is required by rule or policy to retire from a position or role.
  • B. receivesPensionFrom
    Indicates that one entity is the source or provider of a pension that another entity receives.
  • C. appliesToRetirementStatus
    Indicates that the subject is relevant or applicable specifically to an entity’s retirement status or condition.
  • D. earliestRetirementPensionStartAge
    Indicates the minimum age at which an individual is first allowed to begin receiving retirement pension benefits.
  • E. hasFullRetirementAgeRange
    Indicates that there is a defined span of ages during which an entity is considered to have reached full retirement status.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a3a24881908d81d634622fbbcc completed April 14, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69dd464b1ab48190ae50bfc902bf6ef7 completed April 13, 2026, 7:38 p.m.
PDg Predicate description generation batch_69de01ed2098819088ec45069f6f2609 completed April 14, 2026, 8:59 a.m.
Created at: April 9, 2026, 10:15 p.m.