Triple

T2346997
Position Surface form Disambiguated ID Type / Status
Subject Title XVIII of the Social Security Act E45153 entity
Predicate instanceOf P0 FINISHED
Object Medicare statute C251 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: Medicare statute
Context triple: [Title XVIII of the Social Security Act, instanceOf, Medicare statute]
  • 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. statute chosen
    A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
  • C. health insurance continuation law
    A health insurance continuation law is a legal requirement that allows individuals to maintain their employer-sponsored health coverage for a limited time after events like job loss, reduced hours, or certain life changes that would otherwise end their eligibility.
  • D. constitutional statute
    A constitutional statute is a fundamental law enacted by a legislature that, while formally an ordinary statute, has quasi-constitutional status because it implements, structures, or protects core constitutional principles and cannot be amended or repealed without special procedures or heightened scrutiny.
  • E. canonical legislation
    Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
  • 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_69a88917935081909b755dbf38e81024 completed March 4, 2026, 7:33 p.m.
Created at: March 4, 2026, 7:52 p.m.