Triple
T5981254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elan Pharmaceuticals |
E133121
|
entity |
| Predicate | laterResumed |
P7824
|
FINISHED |
| Object | Tysabri marketing |
—
|
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: Tysabri marketing | Statement: [Elan Pharmaceuticals, laterResumed, Tysabri marketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterResumed Context triple: [Elan Pharmaceuticals, laterResumed, Tysabri marketing]
-
A.
resumedIn
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
B.
resumesAfter
chosen
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
C.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
laterSought
Indicates that one entity attempted to obtain, pursue, or request another entity at a subsequent time relative to some prior reference point.
-
E.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a67c3248190ba35a7121eb49672 |
completed | March 22, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.