Triple

T33637302
Position Surface form Disambiguated ID Type / Status
Subject RE-LY trial E861731 entity
Predicate warfarinTargetINR P177449 FINISHED
Object 2.0–3.0 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.0–3.0 | Statement: [RE-LY trial, warfarinTargetINR, 2.0–3.0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: warfarinTargetINR
Context triple: [RE-LY trial, warfarinTargetINR, 2.0–3.0]
  • A. coagulationTime
    Indicates the duration required for a substance, typically a liquid like blood or a solution, to undergo coagulation and form a solid or semi-solid clot.
  • B. hasNarrowTherapeuticIndex
    Indicates that the drug’s effective dose is close to its toxic dose, requiring precise dosing and monitoring to avoid adverse effects.
  • C. coagulationAgent
    Indicates that one entity serves as or contains a substance that promotes or causes the coagulation (clotting or thickening) of another entity.
  • D. 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.
  • E. hasCommonStartingDose_mgPerDay
    Indicates that two treatments share the same typical initial dosage, measured in milligrams 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_69f3498280c48190bcc3494017d14234 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fb93224881908fc66fe76115fcdb completed May 3, 2026, 7:38 a.m.
PD Predicate disambiguation batch_69f6f96badb08190994442c2aba840b1 completed May 3, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f6fb17d5ec81909091e37e1ddbe577 completed May 3, 2026, 7:36 a.m.
Created at: May 1, 2026, 1:42 a.m.