Triple

T23100133
Position Surface form Disambiguated ID Type / Status
Subject destruction of Krypton E576001 entity
Predicate alternativeCause P146054 FINISHED
Object Brainiac’s actions (in some continuities) 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: Brainiac’s actions (in some continuities) | Statement: [destruction of Krypton, alternativeCause, Brainiac’s actions (in some continuities)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alternativeCause
Context triple: [destruction of Krypton, alternativeCause, Brainiac’s actions (in some continuities)]
  • A. possibleCauseOf chosen
    Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
  • B. causeOf
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • C. eligibleCause
    Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
  • D. causeStatus
    Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
  • E. causeSupported
    Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
  • 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_69e245c060b48190a9bd61a47a16db17 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18de81060819084ab618f05aae583 completed April 29, 2026, 4:49 a.m.
PD Predicate disambiguation batch_69ef89e5ce748190b2c3ac3843484127 completed April 27, 2026, 4:08 p.m.
Created at: April 17, 2026, 3:58 p.m.