Triple

T33388490
Position Surface form Disambiguated ID Type / Status
Subject pomalidomide E854983 entity
Predicate hasBoxedWarningFor P134652 FINISHED
Object embryo-fetal toxicity 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: embryo-fetal toxicity | Statement: [pomalidomide, hasBoxedWarningFor, embryo-fetal toxicity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBoxedWarningFor
Context triple: [pomalidomide, hasBoxedWarningFor, embryo-fetal toxicity]
  • A. hasBlackBoxWarningRegion chosen
    Indicates that a medication or product carries a black box (boxed) safety warning that is applicable within a specified regulatory region or jurisdiction.
  • B. warnedWith
    Indicates that one entity issued a warning to another entity using or accompanied by a particular medium, content, or instrument.
  • C. hasAccessWarning
    Indicates that an entity is associated with a notice or alert about restricted, risky, or limited access to another entity or resource.
  • D. warnsAbout
    Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
  • E. bodyDisplayedAsWarningBy
    Indicates that a body (e.g., content or message) is presented in a warning style or context by a particular agent or system.
  • 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_69fd5bf69acc819092a01e4259785dc3 completed May 8, 2026, 3:43 a.m.
PD Predicate disambiguation batch_69fd59b3f4ac8190a7f9dd3142da6e09 completed May 8, 2026, 3:34 a.m.
Created at: May 1, 2026, 1:35 a.m.