Triple
T37464691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonqueen Alexstrasza |
E931004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hearthstone card representing Alexstrasza |
C65686
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Hearthstone card representing Alexstrasza Context triple: [Dragonqueen Alexstrasza, instanceOf, Hearthstone card representing Alexstrasza]
-
A.
Hearthstone hero card
A Hearthstone hero card is a special card that replaces your current hero, granting a new hero power and often an immediate powerful effect that can significantly alter the course of the game.
-
B.
Hearthstone character
A Hearthstone character is a digital card-based hero or minion with specific abilities, stats, and traits that players use strategically in matches within the Hearthstone game.
-
C.
Hearthstone hero
A Hearthstone hero is the primary character a player embodies in a match, representing a specific class with unique powers, health, and thematic identity that defines their playstyle.
-
D.
Hearthstone card variant
chosen
A Hearthstone card variant is a conceptual template representing a specific version of a card, including its unique attributes, effects, and interactions that distinguish it from other cards and versions within the game.
-
E.
Hearthstone Rogue card
A Hearthstone Rogue card is a collectible card belonging to the Rogue class that typically emphasizes combo-based effects, stealth, and efficient removal to support a tempo- or control-oriented playstyle.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:17 p.m.