Triple
T8928841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ischemic stroke |
E212601
|
entity |
| Predicate | hasPrevention |
P82365
|
FINISHED |
| Object | antiplatelet prophylaxis |
—
|
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: antiplatelet prophylaxis | Statement: [ischemic stroke, hasPrevention, antiplatelet prophylaxis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrevention Context triple: [ischemic stroke, hasPrevention, antiplatelet prophylaxis]
-
A.
prevented
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
B.
isPreventableBy
chosen
Indicates that the occurrence or effect of one entity can be avoided or stopped through the action, intervention, or influence of another entity.
-
C.
worksToPrevent
Indicates an entity actively takes measures or engages in actions to stop, reduce, or avoid the occurrence or impact of another entity or condition.
-
D.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
E.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc667470308190a75ba63de803e3a2 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.