Triple
T37513835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zakarum |
E932580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diablo universe faction |
C64391
|
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: Diablo universe faction Context triple: [Zakarum, instanceOf, Diablo universe faction]
-
A.
Diablo universe location
A Diablo universe location is any distinct place within the Diablo game world—such as towns, dungeons, regions, or realms—characterized by its lore, environment, inhabitants, and role in the overarching narrative and gameplay.
-
B.
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.
-
C.
Diablo quest
A Diablo quest is a structured in-game mission or storyline segment that guides the player through specific objectives, challenges, and narrative events within the Diablo universe.
-
D.
Destiny universe faction
A Destiny universe faction is an organized group of characters, species, or entities within the Destiny setting that shares a common ideology, goal, or allegiance and collectively shapes the game's narrative, conflicts, and world dynamics.
-
E.
location in the Diablo universe
A location in the Diablo universe is any distinct, lore-rich place—such as towns, dungeons, wilderness areas, or realms—where characters can explore, battle enemies, and experience story events within Sanctuary and its connected planes.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.