Triple
T38022578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Rastakhan |
E948680
|
entity |
| Predicate | hearthstoneClass |
P100346
|
FINISHED |
| Object | Shaman |
—
|
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: Shaman | Statement: [King Rastakhan, hearthstoneClass, Shaman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearthstoneClass Context triple: [King Rastakhan, hearthstoneClass, Shaman]
-
A.
gameRoleInHearthstone
Indicates that an entity has a specific role or function within the game Hearthstone.
-
B.
deckArchetype
Indicates a classification relationship where a specific deck is associated with a particular strategic archetype or style of play.
-
C.
relatedClassInWarcraft
Indicates that two entities are related through a class association within the Warcraft universe, such as sharing, corresponding to, or being mapped between specific Warcraft character classes.
-
D.
cardRace
Indicates that one entity participates in or is associated with a competitive race involving cards or card-based vehicles relative to another entity.
-
E.
heroClass
chosen
Indicates the character class or role that a hero belongs to within a given system or context.
- 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_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.