Triple
T37463911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrior |
E930986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World of Warcraft class |
C66040
|
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 class Context triple: [Warrior, instanceOf, World of Warcraft class]
-
A.
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.
-
B.
character from Warcraft franchise
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.
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.
-
D.
rank in the Warcraft universe
A rank in the Warcraft universe represents a hierarchical position or title that signifies an individual’s authority, status, and responsibilities within a specific faction, organization, or military structure.
-
E.
Warcraft universe object
A Warcraft universe object is any tangible or magical entity—such as artifacts, structures, creatures, or environmental elements—originating from or existing within the lore, worlds, and cosmology of the Warcraft franchise.
- F. None of above. chosen
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.