Triple

T17454274
Position Surface form Disambiguated ID Type / Status
Subject Vitex agnus-castus E424988 entity
Predicate potentialAdverseEffect P39645 FINISHED
Object gastrointestinal upset 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: gastrointestinal upset | Statement: [Vitex agnus-castus, potentialAdverseEffect, gastrointestinal upset]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: potentialAdverseEffect
Context triple: [Vitex agnus-castus, potentialAdverseEffect, gastrointestinal upset]
  • A. possibleSideEffect chosen
    Indicates that one entity may occur as a side effect or unintended consequence of another entity or action.
  • B. hasCommonAdverseEffect
    Indicates that two or more entities share at least one adverse effect that occurs in response to them.
  • C. commonAdverseReactions
    Indicates that the related entities are linked through adverse reactions or side effects that frequently occur in association with one another.
  • D. 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).
  • E. predictedEffect
    Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
  • 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_69d889db0ba481908402409af3b37917 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4514129f08190ae7581d2915a0373 completed April 19, 2026, 3:51 a.m.
PD Predicate disambiguation batch_69e3b4f0e3fc819094e466b74622c956 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:47 a.m.