Triple
T16852014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biktarvy |
E409696
|
entity |
| Predicate | isCompleteRegimen |
P125217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Biktarvy, isCompleteRegimen, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCompleteRegimen Context triple: [Biktarvy, isCompleteRegimen, true]
-
A.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
B.
isCompleteFor
Indicates that one entity fully satisfies or finishes the requirements, scope, or intended purpose of another entity.
-
C.
isCompleteOn
Indicates that an activity, task, or process has been fully finished or achieved by a specific point in time or on a specific date.
-
D.
hasLoadingDoseRegimen
Indicates that an entity is associated with a specific initial (loading) dosing regimen administered to rapidly achieve a desired therapeutic level.
-
E.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.