Triple

T22336410
Position Surface form Disambiguated ID Type / Status
Subject Plan L E552156 entity
Predicate hasBenefitDesign P147811 FINISHED
Object limits beneficiary’s annual out-of-pocket costs for covered services 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: limits beneficiary’s annual out-of-pocket costs for covered services | Statement: [Plan L, hasBenefitDesign, limits beneficiary’s annual out-of-pocket costs for covered services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBenefitDesign
Context triple: [Plan L, hasBenefitDesign, limits beneficiary’s annual out-of-pocket costs for covered services]
  • A. hasBenefit
    Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
  • B. hasBenefitType
    Indicates that an entity is associated with a specific category or type of benefit it provides or receives.
  • C. hasDifferentBenefitsThan
    Indicates that the benefits provided by one entity are not the same as those provided by another entity.
  • D. isIndividualBenefit
    Indicates that something provides a benefit or advantage to a single individual rather than to a group or collective.
  • E. benefitAppliesTo
    Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
  • 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_69e11e494eec81909c4d2d51f69499d9 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1577f2f208190ac6270ac4581fa15 completed April 29, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e7300c20088190a59e5bf9e70384f3 completed April 21, 2026, 8:06 a.m.
PDg Predicate description generation batch_69e7342ce08c8190bc0a7085f4a952e7 completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 8:43 p.m.