Triple
T33292202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ondexxya |
E852345
|
entity |
| Predicate | targetsDrug |
P37016
|
FINISHED |
| Object | apixaban |
—
|
NE NERFINISHED |
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: apixaban | Statement: [Ondexxya, targetsDrug, apixaban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsDrug Context triple: [Ondexxya, targetsDrug, apixaban]
-
A.
targetsProtein
Indicates that one entity is directed toward, binds to, or is intended to affect a specific protein as its primary molecular target.
-
B.
targetsDiseaseVector
Indicates that an entity is directed at, designed to affect, or intended to control a particular disease-carrying vector organism.
-
C.
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.
-
D.
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).
-
E.
targetsReceptor
Indicates that one entity is directed toward, binds to, or is designed to act upon a specific receptor.
- 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_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 1:32 a.m.