Triple

T31421689
Position Surface form Disambiguated ID Type / Status
Subject Evolver universe E801546 entity
Predicate supportsStoryType P24486 FINISHED
Object superhero fiction 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: superhero fiction | Statement: [Evolver universe, supportsStoryType, superhero fiction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsStoryType
Context triple: [Evolver universe, supportsStoryType, superhero fiction]
  • A. supportsNarrativeOf
    Indicates that one entity provides evidence, context, or structure that upholds, reinforces, or advances the storyline or interpretive account expressed by another entity.
  • B. supportsType chosen
    Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
  • C. supportsNarrativeElement
    Indicates that one element provides justification, reinforcement, or structural backing for a particular narrative element within a story or discourse.
  • D. supportsNarrativeText
    Indicates that one entity provides justification, evidence, or contextual backing that helps explain or validate the narrative content expressed by another entity.
  • E. supportsTestType
    Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
  • 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_69f348c26f048190b4adadd71b4596c5 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e5174c8190a0bdde7e381b7624 completed May 12, 2026, 7:05 p.m.
Created at: April 30, 2026, 8:48 p.m.