Triple
T37592123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephalem |
E935285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diablo universe species |
C64457
|
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 species Context triple: [Nephalem, instanceOf, Diablo universe species]
-
A.
Diablo universe faction
A Diablo universe faction is an organized group or power bloc within the Diablo setting, defined by shared goals, ideology, or allegiance (such as demons, angels, or mortal orders) that influences the world’s conflicts and storylines.
-
B.
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.
-
C.
Underworld franchise species
Underworld franchise species are the distinct supernatural races—primarily Vampires, Lycans (werewolves), and their hybrids—whose unique origins, abilities, and rivalries drive the mythology and conflicts of the Underworld film universe.
-
D.
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.
-
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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.