Triple

T37457706
Position Surface form Disambiguated ID Type / Status
Subject Shadowreaper Anduin E930839 entity
Predicate heroPowerText P99991 FINISHED
Object Hero Power: Deal 2 damage. After you play a card, refresh this. 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: Hero Power: Deal 2 damage. After you play a card, refresh this. | Statement: [Shadowreaper Anduin, heroPowerText, Hero Power: Deal 2 damage. After you play a card, refresh this.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heroPowerText
Context triple: [Shadowreaper Anduin, heroPowerText, Hero Power: Deal 2 damage. After you play a card, refresh this.]
  • A. heroPower
    Indicates that an entity possesses or is associated with a particular heroic power or special ability.
  • B. heroPowerName
    Indicates the specific power or ability associated with a hero.
  • C. heroPowerEffect chosen
    Indicates the specific impact or outcome that a hero’s power has when it is used.
  • D. hasHeroPower
    Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
  • E. featuresCharacterWithSuperpowers
    Indicates that the subject includes or portrays a character who possesses superhuman abilities or powers.
  • 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbbc49da8c8190902bbb05d2477cab completed May 6, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69fbb13f34b08190bbbb220ac1e6e666 completed May 6, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:17 p.m.