Triple
T15799115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aconitum |
E383052
|
entity |
| Predicate | symptomOfPoisoning |
P54346
|
FINISHED |
| Object | cardiac arrhythmia |
—
|
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: cardiac arrhythmia | Statement: [Aconitum, symptomOfPoisoning, cardiac arrhythmia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symptomOfPoisoning Context triple: [Aconitum, symptomOfPoisoning, cardiac arrhythmia]
-
A.
poisonUsed
Indicates that one entity employed poison as a means to harm, kill, or incapacitate another entity.
-
B.
toxinEffect
chosen
Indicates the harmful impact or physiological response caused by a toxin on a target entity.
-
C.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
-
D.
venomous
Indicates that an organism possesses venom and can inject or deliver it to another organism, typically as a means of defense or predation.
-
E.
toxinType
Indicates the specific kind or category of toxin associated with an 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4e00d348190bc98917c4098ec2f |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.