Triple

T35008097
Position Surface form Disambiguated ID Type / Status
Subject Doom Patrol #99 E1009865 entity
Predicate introducesCharacterToUniverse P151722 FINISHED
Object Beast Boy 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: Beast Boy | Statement: [Doom Patrol #99, introducesCharacterToUniverse, Beast Boy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducesCharacterToUniverse
Context triple: [Doom Patrol #99, introducesCharacterToUniverse, Beast Boy]
  • A. introducesFictionalCharacter chosen
    Indicates that one entity is responsible for first presenting or bringing a fictional character into a narrative work or story.
  • B. introducesFictionalUniverse
    Indicates that an entity is responsible for originating or first presenting a particular fictional universe or setting.
  • C. introducesCharacterSpecies
    Indicates that an entity presents or brings into a context the species to which a character belongs.
  • D. introducesSuperhero
    Indicates that one entity presents or brings a superhero character into a story, context, or situation for the first time.
  • E. inUniverseCharacter
    Indicates that a character exists within, and is part of, the fictional universe or continuity defined by a particular work or franchise.
  • 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_69f76dcb716881909f75e4fd60ab2284 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fe12a899d4819080d48423f32eace9 completed May 8, 2026, 4:43 p.m.
PD Predicate disambiguation batch_69fe0d7f6aa08190a1d2dfc025d4e0dc completed May 8, 2026, 4:21 p.m.
Created at: May 3, 2026, 4:01 p.m.