Triple
T16284855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinea worm disease |
E395363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neglected tropical disease |
C17715
|
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 Context triple: [Guinea worm disease, instanceOf, neglected tropical disease]
-
A.
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.
-
B.
infectious disease
An infectious disease is a disorder caused by pathogenic microorganisms such as bacteria, viruses, fungi, or parasites that can be transmitted directly or indirectly from one host to another.
-
C.
disease
chosen
A disease is an abnormal condition of a living organism that impairs normal functioning and is typically manifested by distinguishing signs and symptoms.
-
D.
parasitic nematode
A parasitic nematode is a microscopic to macroscopic roundworm that lives in or on a host organism, deriving nutrients at the host’s expense and often causing disease or physiological harm.
-
E.
fungal disease
A fungal disease is a pathological condition in plants, animals, or humans caused by parasitic fungi that invade tissues, disrupt normal physiological functions, and often spread via spores in conducive environmental conditions.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.