Triple

T35511222
Position Surface form Disambiguated ID Type / Status
Subject Shornhelm E1026289 entity
Predicate instanceOf P0 FINISHED
Object settlement in The Elder Scrolls C32075 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: settlement in The Elder Scrolls
Context triple: [Shornhelm, instanceOf, settlement in The Elder Scrolls]
  • A. settlement in Westeros
    A settlement in Westeros is a populated location—ranging from small villages and holdfasts to large towns and fortified cities—where people live, work, and organize under the rule or protection of a local lord or ruling house.
  • B. location in The Elder Scrolls chosen
    A location in The Elder Scrolls is any distinct, explorable place within the game world—such as cities, dungeons, wilderness areas, or landmarks—defined by its geography, lore, inhabitants, and interactive elements.
  • C. settlement in Middle-earth
    A settlement in Middle-earth is a localized community or habitation—such as a village, town, city, or stronghold—where peoples of Tolkien’s world live, work, and interact within a distinct cultural, geographic, and political context.
  • D. organization in The Elder Scrolls
    An organization in The Elder Scrolls is a structured group of individuals—such as guilds, factions, cults, or orders—united by shared goals, beliefs, or functions that influence the political, social, or magical landscape of the game world.
  • 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.

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_69f76dfd61208190b93ec6dc439cab41 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:04 p.m.