Triple
T23643229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Programme for Onchocerciasis Control |
E583956
|
entity |
| Predicate | targetsPathogen |
P51612
|
FINISHED |
| Object | Onchocerca volvulus |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Onchocerca volvulus | Statement: [African Programme for Onchocerciasis Control, targetsPathogen, Onchocerca volvulus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsPathogen Context triple: [African Programme for Onchocerciasis Control, targetsPathogen, Onchocerca volvulus]
-
A.
addressesPathogen
chosen
Indicates that an action, intervention, or measure is directed toward counteracting, managing, or mitigating a specific pathogen.
-
B.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
C.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
D.
targetsVirus
Indicates that one entity is directed against, acts upon, or is specifically intended to affect a virus.
-
E.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
- F. None of above.
Provenance (3 batches)
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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2821cb881909b1ab77aa77208e0 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.