Triple

T22245473
Position Surface form Disambiguated ID Type / Status
Subject Plan K E549829 entity
Predicate instanceOf P0 FINISHED
Object standardized Medigap plan C30957 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: standardized Medigap plan
Context triple: [Plan K, instanceOf, standardized Medigap plan]
  • A. Medicare coverage component
    A Medicare coverage component is a distinct part or feature of a Medicare plan that defines specific benefits, services, and cost-sharing arrangements available to beneficiaries.
  • B. multiemployer benefit plan
    A multiemployer benefit plan is a collectively bargained employee benefit arrangement maintained by two or more unrelated employers, typically within the same industry, and administered by a joint board of trustees representing both employers and labor unions.
  • C. health and welfare benefit plan
    A health and welfare benefit plan is an employer- or organization-sponsored program that provides employees and their dependents with non-retirement benefits such as medical, dental, vision, disability, and life insurance coverage.
  • D. public health insurance scheme chosen
    A public health insurance scheme is a government-organized program that pools public funds to provide defined healthcare coverage and financial protection against medical costs for eligible populations.
  • E. long-term care insurance program
    A long-term care insurance program is a financial protection plan that helps cover the costs of extended care services—such as nursing homes, assisted living, or in-home care—when individuals can no longer perform basic daily activities independently.
  • F. None of above.

Provenance (1 batch)

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.
Created at: April 16, 2026, 8:38 p.m.