Triple
T37456295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspect of Justice |
E930808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diablo universe object |
C14415
|
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 object Context triple: [Aspect of Justice, instanceOf, Diablo universe object]
-
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
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.
in-universe object
chosen
An in-universe object is any tangible or intangible item that exists within a fictional world's reality and can be perceived, used, or referenced by characters in that setting.
-
D.
Doom monster
A Doom monster is a hostile, often demonic entity in the Doom universe designed to challenge players with distinct attack patterns, behaviors, and vulnerabilities.
-
E.
object in Tolkien legendarium
An object in the Tolkien legendarium is any physical or crafted item—mundane or magical—that exists within Tolkien’s fictional world and can be used, possessed, or referenced by its characters.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.