Triple

T23729614
Position Surface form Disambiguated ID Type / Status
Subject Stop TB Strategy E586375 entity
Predicate instanceOf P0 FINISHED
Object tuberculosis control framework C1784 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: tuberculosis control framework
Context triple: [Stop TB Strategy, instanceOf, tuberculosis control framework]
  • A. tuberculosis control program
    A tuberculosis control program is a coordinated public health initiative designed to prevent, detect, treat, and monitor tuberculosis cases in a population to reduce transmission, morbidity, and mortality.
  • B. neglected tropical disease control program
    A neglected tropical disease control program is an organized, often multi-sectoral public health initiative designed to prevent, reduce, and eventually eliminate the burden of neglected tropical diseases in affected populations through interventions such as mass drug administration, vector control, surveillance, health education, and health system strengthening.
  • C. tuberculosis sanatorium
    A tuberculosis sanatorium is a specialized medical facility, often in a rural or high-altitude setting, dedicated to the long-term isolation, treatment, and convalescent care of patients with tuberculosis.
  • D. antitubercular agent
    An antitubercular agent is a drug used to prevent or treat infections caused by Mycobacterium tuberculosis by inhibiting its growth or killing the bacteria.
  • E. WHO framework chosen
    The WHO framework is a structured, evidence-based model developed by the World Health Organization to guide global health policy, planning, and interventions across health systems, disease control, and population well-being.
  • 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_69e24907dc9c8190be074c9c96a0ec2d completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 7:09 p.m.