Triple

T33292185
Position Surface form Disambiguated ID Type / Status
Subject Andexxa E852344 entity
Predicate hasPharmacologicTarget P37016 FINISHED
Object factor Xa inhibitors 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: factor Xa inhibitors | Statement: [Andexxa, hasPharmacologicTarget, factor Xa inhibitors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPharmacologicTarget
Context triple: [Andexxa, hasPharmacologicTarget, factor Xa inhibitors]
  • A. hasMolecularTarget chosen
    Indicates that one entity (such as a drug or compound) is directed toward, binds to, or specifically interacts with a particular molecular target (such as a protein, receptor, or gene).
  • B. isTherapeuticTargetIn
    Indicates that a biological entity (e.g., gene, protein, pathway) is used or proposed as a therapeutic target within a specified disease, condition, or treatment context.
  • C. hasPharmacologicalEffect
    Indicates that one entity produces a specific pharmacological effect or action on another entity.
  • D. hasDrugBankID
    Indicates that an entity is associated with a specific identifier from the DrugBank database.
  • E. targetsProtein
    Indicates that one entity is directed toward, binds to, or is intended to affect a specific protein as its primary molecular target.
  • 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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f7431c0eec81909ead443e07d75e18 completed May 3, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69f74143cf708190a12d487884298437 completed May 3, 2026, 12:36 p.m.
Created at: May 1, 2026, 1:32 a.m.