Triple
T16501643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrantel pamoate |
E400813
|
entity |
| Predicate | effectOnParasite |
P84339
|
FINISHED |
| Object | causes detachment of worms from intestinal wall |
—
|
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: causes detachment of worms from intestinal wall | Statement: [Pyrantel pamoate, effectOnParasite, causes detachment of worms from intestinal wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnParasite Context triple: [Pyrantel pamoate, effectOnParasite, causes detachment of worms from intestinal wall]
-
A.
parasitizes
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
B.
effectOnGhosts
Indicates the influence or impact that something has on ghosts, such as how it alters their state, behavior, or abilities.
-
C.
effectivenessAgainst
chosen
Indicates how well one entity performs in countering, influencing, or mitigating the impact of another entity.
-
D.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
E.
toxinEffect
Indicates the harmful impact or physiological response caused by a toxin on a target entity.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4f7b7c8190adb5a113f798484f |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.