Triple

T19772861
Position Surface form Disambiguated ID Type / Status
Subject Lyrica E474930 entity
Predicate isNotRecommendedWith P97026 FINISHED
Object concurrent alcohol use due to additive CNS depression 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: concurrent alcohol use due to additive CNS depression | Statement: [Lyrica, isNotRecommendedWith, concurrent alcohol use due to additive CNS depression]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNotRecommendedWith
Context triple: [Lyrica, isNotRecommendedWith, concurrent alcohol use due to additive CNS depression]
  • A. notRecommendedBy
    Indicates that one entity explicitly advises against or does not endorse another entity.
  • B. shouldNotBeUsedWith chosen
    Indicates that one entity is not recommended or is prohibited from being used in combination with another entity.
  • C. shouldNotBeUsedIn
    Indicates that one entity is not appropriate, allowed, or recommended for use within the context, scope, or situation defined by another entity.
  • D. notCompatibleWith
    Indicates that two entities cannot function together properly or are unsuitable for joint use or interaction.
  • E. discouragedUsageReason
    Indicates the reason why a particular usage, action, or practice is considered discouraged.
  • 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6535e450c8190a2628245ae0d0bd3 completed April 20, 2026, 4:25 p.m.
PD Predicate disambiguation batch_69e53053ed2881908400becdfada7fd3 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:48 p.m.