Triple
T33388672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teprotumumab |
E854987
|
entity |
| Predicate | hasSubsequentDose |
P199641
|
FINISHED |
| Object | 20 mg/kg |
—
|
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: 20 mg/kg | Statement: [Teprotumumab, hasSubsequentDose, 20 mg/kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentDose Context triple: [Teprotumumab, hasSubsequentDose, 20 mg/kg]
-
A.
hasInitialDose
Indicates that an entity has received or is assigned a first or starting dose of a treatment, medication, or substance.
-
B.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
C.
hasMaintenanceDose
Indicates that an entity is associated with a specific ongoing dose used to maintain a desired therapeutic effect after initial treatment.
-
D.
hasSubsequentTreatment
Indicates that one treatment occurs after and in continuation of another treatment in a temporal sequence.
-
E.
hasDefinedDailyDose
Indicates that an entity has an established standard amount intended to be taken or used per day.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
| PDg | Predicate description generation | batch_69ff49f7db2c819094d488d13985334c |
completed | May 9, 2026, 2:51 p.m. |
Created at: May 1, 2026, 1:35 a.m.