Triple
T3883268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Blindness Program |
E92875
|
entity |
| Predicate | targetsDisease |
P20980
|
FINISHED |
| Object | river blindness |
—
|
LITERAL FINISHED |
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: river blindness | Statement: [River Blindness Program, targetsDisease, river blindness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsDisease Context triple: [River Blindness Program, targetsDisease, river blindness]
-
A.
hasTargetDisease
chosen
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
B.
humanDisease
Indicates that the subject is a disease that affects humans.
-
C.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
D.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
-
E.
relatedDiseaseComplex
Indicates that there is a complex or multifaceted disease relationship between the associated entities, often involving multiple conditions, factors, or mechanisms.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec8e8b3481909617ca0e37f8a6d4 |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.