Triple
T16851916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truvada |
E409694
|
entity |
| Predicate | isNotEffectiveAgainst |
P84339
|
FINISHED |
| Object | established HIV infection when used alone |
—
|
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: established HIV infection when used alone | Statement: [Truvada, isNotEffectiveAgainst, established HIV infection when used alone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotEffectiveAgainst Context triple: [Truvada, isNotEffectiveAgainst, established HIV infection when used alone]
-
A.
effectivenessAgainst
chosen
Indicates how well one entity performs in countering, influencing, or mitigating the impact of another entity.
-
B.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
C.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
D.
cannotBeDamagedBy
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, 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.