Triple
T30675417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magik |
E780895
|
entity |
| Predicate | resurrection |
P115338
|
FINISHED |
| Object | died of the Legacy Virus and later returned to life |
—
|
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: died of the Legacy Virus and later returned to life | Statement: [Magik, resurrection, died of the Legacy Virus and later returned to life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resurrection Context triple: [Magik, resurrection, died of the Legacy Virus and later returned to life]
-
A.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
B.
methodOfResurrection
Indicates the specific process or means by which an entity is brought back to life or restored from death.
-
C.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
D.
revivedAfter
chosen
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
-
E.
resurrectionMarks
Indicates that one entity bears signs or evidence that it has been brought back to life or restored after death or destruction by another entity or process.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b17a7608190a6568c48d8128dfe |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.