Triple
T28740079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leishmania donovani |
E731212
|
entity |
| Predicate | associatedSymptom |
P56351
|
FINISHED |
| Object | prolonged fever |
—
|
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: prolonged fever | Statement: [Leishmania donovani, associatedSymptom, prolonged fever]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSymptom Context triple: [Leishmania donovani, associatedSymptom, prolonged fever]
-
A.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
B.
isUsedForSymptom
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
C.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
-
D.
hasPossibleSymptom
chosen
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
E.
lesionAssociatedWithSymptom
Indicates that a particular lesion is linked to, or occurs together with, a specific symptom.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: April 28, 2026, 6:02 a.m.