Triple
T12243898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viagra |
E291801
|
entity |
| Predicate | contraindicatedWith |
P23156
|
FINISHED |
| Object | nitrates |
—
|
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: nitrates | Statement: [Viagra, contraindicatedWith, nitrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contraindicatedWith Context triple: [Viagra, contraindicatedWith, nitrates]
-
A.
hasContraindication
chosen
Indicates that one entity (such as a treatment, drug, or procedure) should not be used or performed in the presence of another entity (such as a condition, factor, or co-medication) because it may cause harm or adverse effects.
-
B.
mustAvoid
Indicates that one entity is required to stay away from, not engage with, or prevent interaction with another entity or condition.
-
C.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
D.
hasCommonAdverseEffect
Indicates that two or more entities share at least one adverse effect that occurs in response to them.
-
E.
consistentWith
Indicates that one entity does not contradict and is compatible or in agreement with another entity, condition, or set of constraints.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.