Triple
T33637323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RE-LY trial |
E861731
|
entity |
| Predicate | patientCondition |
P129457
|
FINISHED |
| Object | increased risk of 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: increased risk of stroke | Statement: [RE-LY trial, patientCondition, increased risk of stroke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patientCondition Context triple: [RE-LY trial, patientCondition, increased risk of stroke]
-
A.
clinicalCondition
chosen
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other entity.
-
B.
medicalConditionAtTime
Indicates that a specified medical condition is present or applicable to an entity during a particular time or time interval.
-
C.
medicalEvent
Indicates that a specific health-related occurrence or clinical incident has taken place involving one or more entities.
-
D.
currentPhysicalStatus
Indicates the present condition or state of an entity’s physical being or body.
-
E.
healthStatusAtAccession
Indicates the condition or state of health an entity has at the time it is formally recorded, admitted, or added to a system or collection.
- 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.