Triple
T33974888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RHINE |
E871107
|
entity |
| Predicate | usesDosingRegimen |
P37228
|
FINISHED |
| Object | personalized treatment interval |
—
|
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: personalized treatment interval | Statement: [RHINE, usesDosingRegimen, personalized treatment interval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDosingRegimen Context triple: [RHINE, usesDosingRegimen, personalized treatment interval]
-
A.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
B.
doseRegimen
chosen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
C.
hasDosingBasis
Indicates that one dosing specification is based on, derived from, or determined according to another dosing-related parameter or standard.
-
D.
hasCommonStartingDose_mgPerDay
Indicates that two treatments share the same typical initial dosage, measured in milligrams per day.
-
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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.