Triple
T33637224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOAC |
E861729
|
entity |
| Predicate | hasReversalStrategy |
P93715
|
FINISHED |
| Object | prothrombin complex concentrate |
—
|
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: prothrombin complex concentrate | Statement: [DOAC, hasReversalStrategy, prothrombin complex concentrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReversalStrategy Context triple: [DOAC, hasReversalStrategy, prothrombin complex concentrate]
-
A.
hasReversalAgent
chosen
Indicates that one entity serves as an agent that can reverse or counteract the effects or action of another entity.
-
B.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
C.
hasCurrentReversalsPerDay
Indicates the number of times per day that the direction of current flow is reversed.
-
D.
isUsedToReverse
Indicates that one entity serves the function of undoing, inverting, or changing the direction or effect of another entity or process.
-
E.
hasReverseFeature
Indicates that one entity possesses a feature that functions in the opposite or reverse manner of another related feature.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:42 a.m.