Triple

T27660255
Position Surface form Disambiguated ID Type / Status
Subject Juvederm E697101 entity
Predicate possibleSeriousAdverseEffect P24552 FINISHED
Object vascular occlusion 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: vascular occlusion | Statement: [Juvederm, possibleSeriousAdverseEffect, vascular occlusion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleSeriousAdverseEffect
Context triple: [Juvederm, possibleSeriousAdverseEffect, vascular occlusion]
  • A. hasSeriousSideEffect chosen
    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).
  • B. possibleSideEffect
    Indicates that one entity may occur as a side effect or unintended consequence of another entity or action.
  • C. hasCommonAdverseEffect
    Indicates that two or more entities share at least one adverse effect that occurs in response to them.
  • D. commonAdverseReactions
    Indicates that the related entities are linked through adverse reactions or side effects that frequently occur in association with one another.
  • E. unexpectedConsequenceOf
    Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
  • 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_69ef590b85a4819083ec7c12bd3c9c10 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f676c440708190a4b9974e95d2291a completed May 2, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69f675fd59608190b246383435e68fce completed May 2, 2026, 10:09 p.m.
Created at: April 27, 2026, 2:36 p.m.