Triple

T29228654
Position Surface form Disambiguated ID Type / Status
Subject Proxima Midnight (MCU) E741002 entity
Predicate resurrectedVersionKilledBy P166443 FINISHED
Object Scarlet Witch (MCU) NE NERFINISHED

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: Scarlet Witch (MCU) | Statement: [Proxima Midnight (MCU), resurrectedVersionKilledBy, Scarlet Witch (MCU)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resurrectedVersionKilledBy
Context triple: [Proxima Midnight (MCU), resurrectedVersionKilledBy, Scarlet Witch (MCU)]
  • A. revivedAfter
    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.
  • B. revivedAs
    Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
  • C. revivedBy
    Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
  • D. resurrectedInStory
    Indicates that an entity is brought back to life within the events or narrative of a particular story.
  • E. killedBy
    Indicates that one entity caused the death of another entity.
  • 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_69f07cbb12bc81908c1971d9de9a8d2a completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6645ba71c81908044ade6ab577018 completed May 2, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f65c24f8b48190af81b575f3c15be5 completed May 2, 2026, 8:18 p.m.
PDg Predicate description generation batch_69f65fb2ead08190b06677d4d6ea1ea8 completed May 2, 2026, 8:33 p.m.
Created at: April 28, 2026, 12:17 p.m.