Triple
T23932408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaya |
E602535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Magic: The Gathering character |
C25535
|
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: Magic: The Gathering character Context triple: [Kaya, instanceOf, Magic: The Gathering character]
-
A.
Magic: The Gathering card
chosen
A Magic: The Gathering card is a game component that represents spells, creatures, lands, or other elements, each with specific rules text, costs, and attributes used to build decks and play the trading card game.
-
B.
Fantastic Beasts character
A Fantastic Beasts character is an individual—human or magical creature—who exists within the Wizarding World of the Fantastic Beasts film series, contributing to its narrative through their unique magical abilities, personal history, and relationships to the broader Harry Potter canon.
-
C.
Harry Potter character
A Harry Potter character is an individual—human or magical creature—who exists within the Harry Potter universe, possessing distinct traits, roles, and relationships that contribute to the series’ narrative and world-building.
-
D.
Hearthstone hero class
A Hearthstone hero class is a distinct playable archetype that defines a player's unique hero power, card pool, and strategic playstyle within the game.
-
E.
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.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 8:58 p.m.