Triple

T33389077
Position Surface form Disambiguated ID Type / Status
Subject Jcovden E854995 entity
Predicate hasAdverseEffects P194197 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: [Jcovden, hasAdverseEffects, injection site pain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdverseEffects
Context triple: [Jcovden, hasAdverseEffects, injection site pain]
  • A. hasCommonAdverseEffect
    Indicates that two or more entities share at least one adverse effect that occurs in response to them.
  • B. hasRareAdverseEffects
    Indicates that an entity is associated with uncommon or infrequently occurring negative or harmful side effects.
  • C. hasSeriousSideEffect
    Indicates that an entity (such as a treatment, drug, or intervention) causes or is associated with a significant or severe adverse effect on another entity (typically a patient or biological system).
  • D. commonAdverseReactions
    Indicates that the related entities are linked through adverse reactions or side effects that frequently occur in association with one another.
  • E. isNegativeEffect
    Indicates that something produces a harmful, undesirable, or adverse impact on another entity or situation.
  • 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_69f3496d54048190a1cb91fdd7caa6ea completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd67191cf88190b53ecbf5be3564e9 completed May 8, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69fd654fdaac81908e67e75194710f06 completed May 8, 2026, 4:23 a.m.
PDg Predicate description generation batch_69fd67182c348190aa84a02e08dbf4e1 completed May 8, 2026, 4:31 a.m.
Created at: May 1, 2026, 1:35 a.m.