Triple
T16946197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovaldi |
E411074
|
entity |
| Predicate | typicalDose |
P37228
|
FINISHED |
| Object | 400 mg once daily in adults |
—
|
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: 400 mg once daily in adults | Statement: [Sovaldi, typicalDose, 400 mg once daily in adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDose Context triple: [Sovaldi, typicalDose, 400 mg once daily in adults]
-
A.
maximumDailyDoseTypicalAdult
Indicates the highest amount of a substance that a typical adult is recommended or allowed to take in one day.
-
B.
typicalDosageCategories
Indicates the standard dosage ranges or categories typically associated with a given treatment, substance, or medication.
-
C.
typicalDosageStyles
Indicates the usual ways or patterns in which a dosage is administered or presented (e.g., standard amounts, frequencies, or formats).
-
D.
doseRegimen
chosen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
E.
hasMaintenanceDose
Indicates that an entity is associated with a specific ongoing dose used to maintain a desired therapeutic effect after initial treatment.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb25e0c8190948e62d9575ae9cd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.