Triple
T37461618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thing from Below |
E930931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shaman-class card |
C64261
|
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: Shaman-class card Context triple: [Thing from Below, instanceOf, Shaman-class card]
-
A.
Shaman card
chosen
A Shaman card represents a mystical spellcaster character who channels elemental or spiritual powers to influence gameplay through unique abilities, buffs, and control effects.
-
B.
Dragon card
A Dragon card represents a powerful, often high-cost creature characterized by flying, formidable combat abilities, and thematic ties to fire, dominance, or ancient magic within a card game.
-
C.
Mech-synergy card
A Mech-synergy card is a game card designed to enhance, trigger, or benefit from interactions specifically between mechanical or robot-type units, amplifying their combined effectiveness when played together.
-
D.
Rogue-class card
A Rogue-class card is a game element representing a stealthy, cunning archetype that specializes in deception, agility, and opportunistic tactics, often featuring abilities like stealth, combo effects, and resource manipulation.
-
E.
Hunter class card
A Hunter class card represents a game entity or ability themed around tracking, ranged attacks, and beast synergy, typically specializing in precision damage and tactical control.
- 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.