Triple

T3430091
Position Surface form Disambiguated ID Type / Status
Subject MultiPlan E72315 entity
Predicate instanceOf P0 FINISHED
Object healthcare cost management company C13270 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: healthcare cost management company
Context triple: [MultiPlan, instanceOf, healthcare cost management company]
  • 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. healthcare organization unit
    A healthcare organization unit is a distinct administrative or functional division within a healthcare system (such as a department, clinic, or ward) that delivers specific health-related services, manages resources, and supports patient care processes.
  • C. healthcare accreditation organization
    A healthcare accreditation organization is an independent body that evaluates and certifies healthcare providers and institutions against established quality and safety standards to ensure consistent, high-quality patient care.
  • D. infrastructure management company
    An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
  • E. medical organization
    A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
  • F. None of above. chosen

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_69ad85ae14308190bcbc25cfa0246c0b completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:15 p.m.