Triple
T28518922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderclap |
E721702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region in Mid-World |
C54198
|
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: region in Mid-World Context triple: [Thunderclap, instanceOf, region in Mid-World]
-
A.
region of Middle-earth
A region of Middle-earth is a geographically defined area within Tolkien’s fictional world, characterized by its distinct landscapes, cultures, histories, and roles in the overarching narrative.
-
B.
medieval region
A medieval region is a geographically defined area during the Middle Ages characterized by distinct political authority, social structures, economic systems, and cultural practices within the broader feudal landscape.
-
C.
location in the Warcraft universe
A location in the Warcraft universe is any distinct, lore-defined place—ranging from continents and kingdoms to cities, dungeons, and landmarks—within Azeroth and its connected realms that serves as a setting for events, quests, and stories.
-
D.
region in Essos
A region in Essos is a distinct geographical and cultural area on the eastern continent of the known world, defined by its unique landscapes, peoples, politics, and economic activities.
-
E.
underworld region
An underworld region is a mythological or symbolic realm located beneath the surface world, typically associated with the dead, hidden forces, or forbidden activities.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:19 a.m.