Triple
T28896909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earthrealm |
E732856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Mortal Kombat |
C55369
|
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 Mortal Kombat Context triple: [Earthrealm, instanceOf, location in Mortal Kombat]
-
A.
location in comics
A location in comics is any specific place or setting—real or fictional—where comic book events occur and characters interact, helping to establish atmosphere, context, and narrative progression.
-
B.
location in the Mario series
A location in the Mario series is any distinct place or environment within the Mario universe—such as kingdoms, worlds, levels, or specific areas—where gameplay, story events, or character interactions occur.
-
C.
location in Marvel Comics
A "location in Marvel Comics" is any fictional place, setting, or environment within the Marvel universe where characters act and stories unfold, ranging from specific cities and planets to dimensions and hidden realms.
-
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 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.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:59 a.m.