Triple
T2371088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Activase |
E46090
|
entity |
| Predicate | timeWindowForAcuteIschemicStroke |
P37859
|
FINISHED |
| Object | within several hours of symptom onset |
—
|
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: within several hours of symptom onset | Statement: [Activase, timeWindowForAcuteIschemicStroke, within several hours of symptom onset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeWindowForAcuteIschemicStroke Context triple: [Activase, timeWindowForAcuteIschemicStroke, within several hours of symptom onset]
-
A.
timeBetweenInjuryAndDeath
Indicates the duration of time that elapses between when an injury occurs and when death subsequently happens.
-
B.
inceptionTime
Indicates the specific point in time when an entity, event, or relationship begins or is first established.
-
C.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc771302481908540e31abb5aeeba |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6443c6c8190b932de2abd8eb28f |
completed | March 7, 2026, 6:31 a.m. |
Created at: March 4, 2026, 7:56 p.m.