Triple
T38022579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Rastakhan |
E948680
|
entity |
| Predicate | hearthstoneType |
P187928
|
FINISHED |
| Object | alternate hero |
—
|
LITERAL FINISHED |
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: alternate hero | Statement: [King Rastakhan, hearthstoneType, alternate hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearthstoneType Context triple: [King Rastakhan, hearthstoneType, alternate hero]
-
A.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
B.
deckArchetype
Indicates a classification relationship where a specific deck is associated with a particular strategic archetype or style of play.
-
C.
iconicTCGCard
Indicates that a trading card game (TCG) card is widely recognized as emblematic or highly representative of its game or format.
-
D.
mechanicalThemeInHearthstone
Indicates that a particular mechanical or gameplay concept is used as a recurring thematic element within the game Hearthstone.
-
E.
gameRoleInHearthstone
chosen
Indicates that an entity has a specific role or function within the game Hearthstone.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.