Triple

T37540673
Position Surface form Disambiguated ID Type / Status
Subject Hallazeal the Ascended E933316 entity
Predicate designerGame P105330 FINISHED
Object Hearthstone: Heroes of Warcraft 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: Hearthstone: Heroes of Warcraft | Statement: [Hallazeal the Ascended, designerGame, Hearthstone: Heroes of Warcraft]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designerGame
Context triple: [Hallazeal the Ascended, designerGame, Hearthstone: Heroes of Warcraft]
  • A. designedGame chosen
    Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
  • B. gameModeDesign
    Indicates that one entity defines or specifies the rules, structure, or configuration of a particular game mode for another entity.
  • C. trapDesigner
    Indicates that one entity is responsible for planning, creating, or setting a trap that is associated with another entity.
  • D. gameDesignSpecialty
    Indicates that one entity has a particular area of specialization or focus within the field of game design in relation to another entity.
  • E. playDesignFeature
    Indicates that a design feature is incorporated into or utilized within a play or gameplay experience.
  • 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_69f76ec999288190ae26ec7b6aea7046 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff7c96e6dc8190b89554480ebcea39 completed May 9, 2026, 6:27 p.m.
PD Predicate disambiguation batch_69ff7c2381748190ad9a2176e0e478cd completed May 9, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:17 p.m.