Triple
T5305298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow jessamine |
E120085
|
entity |
| Predicate | toxicEffect |
P54346
|
FINISHED |
| Object | respiratory failure |
—
|
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: respiratory failure | Statement: [Yellow jessamine, toxicEffect, respiratory failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toxicEffect Context triple: [Yellow jessamine, toxicEffect, respiratory failure]
-
A.
toxinEffect
chosen
Indicates the harmful impact or physiological response caused by a toxin on a target entity.
-
B.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
-
C.
notableToxicity
Indicates that an entity is recognized for having a significant level or history of toxicity, harm, or detrimental effects in its context or interactions.
-
D.
toxinType
Indicates the specific kind or category of toxin associated with an entity.
-
E.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.