Triple
T16284940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dracunculus medinensis |
E395364
|
entity |
| Predicate | hasNoApprovedDrugTreatment |
P122521
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dracunculus medinensis, hasNoApprovedDrugTreatment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoApprovedDrugTreatment Context triple: [Dracunculus medinensis, hasNoApprovedDrugTreatment, true]
-
A.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
B.
treatmentWithheld
Indicates that a treatment that could have been provided to an entity was intentionally not administered or was withheld.
-
C.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
-
D.
hasNotableDrug
Indicates that an entity is associated with a drug that is considered notable or significant in some recognized context.
-
E.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
- F. None of above. chosen
Provenance (4 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24913a55081909a9a5a7a7f4806cc |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.