Triple
T16852003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biktarvy |
E409696
|
entity |
| Predicate | hasSideEffect |
P39645
|
FINISHED |
| Object | nausea |
—
|
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: nausea | Statement: [Biktarvy, hasSideEffect, nausea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideEffect Context triple: [Biktarvy, hasSideEffect, nausea]
-
A.
hasCommonSideEffect
Indicates that two or more treatments, drugs, or interventions share at least one side effect in common.
-
B.
sideEffect
Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
-
C.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
D.
possibleSideEffect
chosen
Indicates that one entity may occur as a side effect or unintended consequence of another entity or action.
-
E.
hasDirectEffect
Indicates that one entity produces an immediate and unmediated impact or change on 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b379b8fc81908d8bc9950c7f8bad |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.