Triple

T2190673
Position Surface form Disambiguated ID Type / Status
Subject Xarelto E49852 entity
Predicate hasProteinBinding P37224 FINISHED
Object high plasma protein binding 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: high plasma protein binding | Statement: [Xarelto, hasProteinBinding, high plasma protein binding]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProteinBinding
Context triple: [Xarelto, hasProteinBinding, high plasma protein binding]
  • A. hasBindingEnergy
    Indicates that one entity possesses or is characterized by a specific amount of binding energy associated with its formation or stability.
  • B. isPegylated
    Indicates that a molecule, typically a drug or therapeutic agent, has been chemically modified by the attachment of polyethylene glycol (PEG) chains.
  • C. proteinContent
    Indicates the amount or proportion of protein present in a given entity or substance.
  • D. isNotBindingOn
    Indicates that an agreement, rule, or obligation does not have legal or enforceable effect on the referenced entity.
  • E. regulatoryInteraction
    Indicates a relationship where one entity modulates, controls, or influences the activity, expression, or function of another entity through regulatory mechanisms.
  • 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_69a88aaba3c48190b351cab9b26989ff completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abbf9e99f08190892d34485c8f2f25 completed March 7, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69abbda32d1881909d1fd83a751fb21c completed March 7, 2026, 5:54 a.m.
PDg Predicate description generation batch_69abbf9c77fc8190a323bcaf644fb2c5 completed March 7, 2026, 6:03 a.m.
Created at: March 4, 2026, 7:46 p.m.