Triple

T33637254
Position Surface form Disambiguated ID Type / Status
Subject idarucizumab E861730 entity
Predicate hasUsualDoseRegimen P37228 FINISHED
Object two consecutive 2.5 g intravenous infusions 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: two consecutive 2.5 g intravenous infusions | Statement: [idarucizumab, hasUsualDoseRegimen, two consecutive 2.5 g intravenous infusions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUsualDoseRegimen
Context triple: [idarucizumab, hasUsualDoseRegimen, two consecutive 2.5 g intravenous infusions]
  • 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. hasCommonStartingDose_mgPerDay
    Indicates that two treatments share the same typical initial dosage, measured in milligrams per day.
  • D. hasDefinedDailyDose
    Indicates that an entity has an established standard amount intended to be taken or used 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_69f3498280c48190bcc3494017d14234 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc5740fc81909774a4f65201a3ff completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 1:42 a.m.