Triple
T37513094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary |
E932564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diablo location |
C30193
|
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 location Context triple: [Sanctuary, instanceOf, Diablo location]
-
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.
location in the Diablo universe
chosen
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.
-
C.
location in the Dreamlands
A location in the Dreamlands represents a distinct, often surreal or otherworldly place within the dream-realm, characterized by its unique geography, atmosphere, and influence on dreamers’ experiences.
-
D.
location in Mortal Kombat
A location in Mortal Kombat is a distinct arena or setting where fighters battle, often featuring interactive elements, environmental hazards, and thematic designs tied to the game's lore and characters.
-
E.
location in Warcraft universe
A location in the Warcraft universe is any distinct, named place—such as a city, region, dungeon, or landmark—within Azeroth or its connected realms that provides geographical context, lore significance, and gameplay functions.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.