Triple
T33292204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ondexxya |
E852345
|
entity |
| Predicate | targetsDrugClass |
P24600
|
FINISHED |
| Object | direct 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: direct factor Xa inhibitors | Statement: [Ondexxya, targetsDrugClass, direct factor Xa inhibitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsDrugClass Context triple: [Ondexxya, targetsDrugClass, direct factor Xa inhibitors]
-
A.
drugClass
Indicates that one entity is classified as a particular pharmacological or therapeutic category of drugs in relation to another entity.
-
B.
hasPharmacologicClass
chosen
Indicates that a drug or medicinal product belongs to a specific pharmacologic class based on its mechanism of action or therapeutic effect.
-
C.
drugClassComponent
Indicates that one entity is a component, ingredient, or member of a specified drug class.
-
D.
drugClassEvaluated
Indicates that the classification or category of a drug has been assessed or analyzed in a given context.
-
E.
protectedDrugClassesInclude
Indicates that the specified set of protected drug classes includes the referenced drug class or classes.
- 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_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 1:32 a.m.