Triple
T3883262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Blindness Program |
E92875
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neglected tropical disease control program |
C14274
|
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: neglected tropical disease control program Context triple: [River Blindness Program, instanceOf, neglected tropical disease control program]
-
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.
malaria control strategy
A malaria control strategy is a coordinated set of interventions and policies designed to prevent, reduce, and ultimately eliminate malaria transmission and disease burden in a target population.
-
C.
World Health Organization program
A World Health Organization program is a coordinated global initiative designed and managed by WHO to address specific public health priorities through research, policy guidance, capacity building, and on-the-ground interventions in member states.
-
D.
disease surveillance program
A disease surveillance program is a systematic, ongoing process of collecting, analyzing, and interpreting health data to detect, monitor, and respond to disease occurrences in a population.
-
E.
polio eradication program
A polio eradication program is a coordinated public health initiative that aims to eliminate poliovirus transmission through widespread vaccination, surveillance, outbreak response, and community engagement.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:20 p.m.