Triple

T8194708
Position Surface form Disambiguated ID Type / Status
Subject District of Columbia health and human services system E191399 entity
Predicate instanceOf P0 FINISHED
Object health and human services system C7556 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: health and human services system
Context triple: [District of Columbia health and human services system, instanceOf, health and human services system]
  • A. health care system
    A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
  • B. public health system chosen
    A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
  • C. health policy
    Health policy is a set of decisions, plans, and actions undertaken by governments or organizations to achieve specific healthcare goals and improve the health outcomes of populations.
  • D. healthcare compensation system
    A healthcare compensation system is a framework that manages and administers payments, reimbursements, and financial incentives for healthcare providers and organizations based on services delivered, performance metrics, and regulatory requirements.
  • E. healthcare administration service
    A healthcare administration service manages the non-clinical operations of healthcare organizations, including scheduling, billing, compliance, records management, and coordination among providers, payers, and patients to ensure efficient and compliant delivery of care.
  • 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_69ca82c6e9548190a4c5ca14516e4417 completed March 30, 2026, 2:03 p.m.
Created at: March 30, 2026, 5:42 p.m.