Triple
T6064921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mounjaro |
E135131
|
entity |
| Predicate | startingDose |
P23153
|
FINISHED |
| Object | 2.5 mg once weekly |
—
|
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: 2.5 mg once weekly | Statement: [Mounjaro, startingDose, 2.5 mg once weekly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingDose Context triple: [Mounjaro, startingDose, 2.5 mg once weekly]
-
A.
doseRegimen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
B.
hasMaintenanceDose
Indicates that an entity is associated with a specific ongoing dose used to maintain a desired therapeutic effect after initial treatment.
-
C.
hasInitialDose
chosen
Indicates that an entity has received or is assigned a first or starting dose of a treatment, medication, or substance.
-
D.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
E.
doseAdjustmentRequiredIn
Indicates that a change in the amount or frequency of a treatment or medication is necessary within a specified context, such as a condition, setting, or patient group.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05723c91c819090b4d4672e72f9f3 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.