Triple
T33292158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andexxa |
E852344
|
entity |
| Predicate | isUsedToReverse |
P176458
|
FINISHED |
| Object | rivaroxaban |
—
|
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: rivaroxaban | Statement: [Andexxa, isUsedToReverse, rivaroxaban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToReverse Context triple: [Andexxa, isUsedToReverse, rivaroxaban]
-
A.
inverseUses
Indicates that one entity is used by another entity, expressing the inverse direction of a "uses" relationship.
-
B.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
C.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
D.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
E.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:32 a.m.