Triple
T33637320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RE-LY trial |
E861731
|
entity |
| Predicate | efficacyOutcome |
P76547
|
FINISHED |
| Object | ischemic stroke |
—
|
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: ischemic stroke | Statement: [RE-LY trial, efficacyOutcome, ischemic stroke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: efficacyOutcome Context triple: [RE-LY trial, efficacyOutcome, ischemic stroke]
-
A.
measuredEffect
chosen
Indicates that an action or process has produced a specific, quantified outcome or impact on something.
-
B.
outcomeSummary
Indicates a concise description or overview of the result or consequences of an action, event, or process.
-
C.
performanceOutcome
Indicates the result, effect, or consequence produced by a particular performance or action.
-
D.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
E.
supportedOutcomeOf
Indicates that one entity serves as evidence, backing, or justification for the outcome or result represented by another entity.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.