Triple
T37465521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanrethad Ebonlocke |
E931024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World of Warcraft non-player character |
C32880
|
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: World of Warcraft non-player character Context triple: [Kanrethad Ebonlocke, instanceOf, World of Warcraft non-player character]
-
A.
World of Warcraft class
A World of Warcraft class is a distinct character archetype that defines a player's combat role, abilities, and playstyle within the game’s fantasy world.
-
B.
character from Warcraft franchise
chosen
A character from the Warcraft franchise is a fictional individual—such as a hero, villain, or supporting figure—who exists within the Warcraft universe’s lore, games, and media, possessing distinct abilities, backstory, and affiliations with its various races and factions.
-
C.
organization in the Warcraft universe
An organization in the Warcraft universe is a structured group of individuals, factions, or races united by a common purpose, ideology, or goal, operating within the lore’s political, military, religious, or economic landscapes.
-
D.
World of Warcraft faction
A World of Warcraft faction is a large in-game organization or alliance of races, characters, and NPCs that shares a common identity, goals, and reputation system, influencing player relationships, quests, and access to resources.
-
E.
Hearthstone character
A Hearthstone character is a digital card-based hero or minion with specific abilities, stats, and traits that players use strategically in matches within the Hearthstone game.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.