Triple

T22245358
Position Surface form Disambiguated ID Type / Status
Subject Plan C E549826 entity
Predicate helpsCover P52868 FINISHED
Object out-of-pocket costs not paid by Original Medicare 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: out-of-pocket costs not paid by Original Medicare | Statement: [Plan C, helpsCover, out-of-pocket costs not paid by Original Medicare]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: helpsCover
Context triple: [Plan C, helpsCover, out-of-pocket costs not paid by Original Medicare]
  • A. mayCover chosen
    Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
  • B. typicallyCovers
    Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
  • C. providesCoverage
    Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
  • D. guaranteeCoverage
    Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
  • E. collectivelyCovers
    Indicates that a group of entities, taken together, fully covers or accounts for a specified set, area, or scope.
  • 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_69e11e41d9408190bd770cf282e22753 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f13217c9f88190aa2ce7d644b57739 completed April 28, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69e72fe1e0cc8190bd13cff2a0846225 completed April 21, 2026, 8:05 a.m.
Created at: April 16, 2026, 8:38 p.m.