Triple
T37555187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleak Redoubt |
E933679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Maldraxxus |
C66074
|
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: location in Maldraxxus Context triple: [Bleak Redoubt, instanceOf, location in Maldraxxus]
-
A.
Covenant house of Maldraxxus
The Covenant house of Maldraxxus is a militaristic necromantic order that forges and commands undead armies to defend the Shadowlands through strength, strategy, and relentless warfare.
-
B.
location in The Elder Scrolls universe
A location in The Elder Scrolls universe is any distinct, explorable place—such as cities, dungeons, regions, or landmarks—within the series’ fictional world that can be visited, referenced, or interacted with in-game or in lore.
-
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 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.
-
E.
location in The Elder Scrolls
A location in The Elder Scrolls is any distinct, explorable place within the game world—such as cities, dungeons, wilderness areas, or landmarks—defined by its geography, lore, inhabitants, and interactive elements.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.