Triple
T33388976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zabdeno |
E854993
|
entity |
| Predicate | hasCommonAdverseReaction |
P23164
|
FINISHED |
| Object | injection site pain |
—
|
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: injection site pain | Statement: [Zabdeno, hasCommonAdverseReaction, injection site pain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonAdverseReaction Context triple: [Zabdeno, hasCommonAdverseReaction, injection site pain]
-
A.
hasCommonAdverseEffect
chosen
Indicates that two or more entities share at least one adverse effect that occurs in response to them.
-
B.
commonAdverseReactions
Indicates that the related entities are linked through adverse reactions or side effects that frequently occur in association with one another.
-
C.
hasAdverseEffects
Indicates that one entity causes or is associated with harmful, negative, or undesired effects on another entity.
-
D.
hasRareAdverseEffects
Indicates that an entity is associated with uncommon or infrequently occurring negative or harmful side effects.
-
E.
hasCommonDrugInteraction
Indicates that two drugs share at least one known interaction that may affect their safety or effectiveness when used together.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:35 a.m.