Triple
T37512499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sin War |
E932550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Diablo universe |
C65055
|
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: event in the Diablo universe Context triple: [Sin War, instanceOf, event in the Diablo universe]
-
A.
event in the Warcraft universe
An event in the Warcraft universe is a significant occurrence or series of actions—such as battles, political upheavals, magical catastrophes, or character-driven turning points—that shapes the history, factions, and ongoing narrative of Azeroth and its connected realms.
-
B.
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.
-
C.
event in The Elder Scrolls universe
An event in The Elder Scrolls universe is a significant occurrence—such as a battle, prophecy fulfillment, political upheaval, or divine intervention—that shapes the history, cultures, and power dynamics of Tamriel and its surrounding realms.
-
D.
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.
-
E.
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.
- 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.