Triple
T36937711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Aerospace Corporation research facility |
E913662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in the Doom universe |
C65933
|
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 the Doom universe Context triple: [Union Aerospace Corporation research facility, instanceOf, location in the Doom universe]
-
A.
Doom megawad
A Doom megawad is a large, fan-made collection of custom levels—typically 15 to 32 maps—packaged as a single WAD file for the classic Doom engine.
-
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.
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.
-
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.
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.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.