Triple

T37463489
Position Surface form Disambiguated ID Type / Status
Subject Hunter (Hearthstone class) E930976 entity
Predicate hasAlternateHero P197041 FINISHED
Object Alleria Windrunner 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: Alleria Windrunner | Statement: [Hunter (Hearthstone class), hasAlternateHero, Alleria Windrunner]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternateHero
Context triple: [Hunter (Hearthstone class), hasAlternateHero, Alleria Windrunner]
  • A. hasSecondaryProtagonist
    Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
  • B. hasAlternateExperience
    Indicates that an entity is associated with a different or substitute experience relative to a primary or standard one.
  • C. hasFictionalAlterEgoOf
    Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
  • D. hasAlterEgoCostume
    Indicates that an entity has a distinct costume specifically associated with its alter ego identity.
  • E. hasSecondaryProtagonistOccupation
    Indicates that a secondary protagonist in a narrative has a specific occupation or job role.
  • 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe744faca881908e11e90e0a35653f completed May 8, 2026, 11:39 p.m.
PD Predicate disambiguation batch_69fe734cbf7081909a552c5cf3b5ea59 completed May 8, 2026, 11:35 p.m.
PDg Predicate description generation batch_69fe744e9ee081909b362fc8609bc744 completed May 8, 2026, 11:39 p.m.
Created at: May 3, 2026, 4:17 p.m.