Triple
T37457176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casino Mage |
E930828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collectible card game deck archetype |
C65446
|
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: collectible card game deck archetype Context triple: [Casino Mage, instanceOf, collectible card game deck archetype]
-
A.
Hearthstone deck archetype
chosen
A Hearthstone deck archetype is a conceptual category of decks that share a core game plan, key cards, and playstyle, such as aggro, control, combo, or midrange.
-
B.
collectible card game
A collectible card game is a game in which players build customized decks from a large pool of unique cards and compete using strategic combinations of those cards’ abilities and interactions.
-
C.
Rogue deck archetype
A rogue deck archetype is a non-mainstream, often unexpected deck build that leverages unconventional card choices or strategies to exploit gaps in the metagame and surprise opponents.
-
D.
trading card game component
A trading card game component is an individual physical or digital element—such as a card, token, or marker—used within a trading card game to represent game entities, actions, or resources and to facilitate gameplay.
-
E.
Warrior deck archetype
A Warrior deck archetype is a strategic card game build centered around Warrior-class cards and synergies, typically emphasizing weapons, armor, and aggressive board control to overwhelm opponents.
- 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.