Triple
T11543507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning Hells |
E273728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diablo universe location |
C30192
|
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 location Context triple: [Burning Hells, instanceOf, Diablo universe location]
-
A.
location in the Foundation universe
A "location in the Foundation universe" represents any distinct physical or spatial setting—such as planets, space stations, sectors, or regions—within the fictional cosmos of Isaac Asimov’s Foundation series, characterized by its geography, political affiliation, culture, and narrative significance.
-
B.
mythological location
A mythological location is an imagined place rooted in folklore, religion, or legend, often imbued with supernatural qualities and symbolic meaning within a culture’s narrative tradition.
-
C.
collection of mythological locations
A collection of mythological locations represents an organized set of legendary places from various myths and folklore traditions, each with its own symbolic meaning, narrative role, and cultural origin.
-
D.
location in the Marvel Universe
A "location in the Marvel Universe" is any distinct place—such as a city, planet, dimension, or specific site—within Marvel's fictional multiverse where characters, events, and stories occur.
-
E.
location in the Marvel Cinematic Universe
A location in the Marvel Cinematic Universe is any distinct place—real or fictional—where events, characters, or organizations appear or operate within the interconnected MCU narrative.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:37 p.m.