Triple

T37471356
Position Surface form Disambiguated ID Type / Status
Subject Aspirant’s Rest E931159 entity
Predicate instanceOf P0 FINISHED
Object in-game location C63513 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: in-game location
Context triple: [Aspirant’s Rest, instanceOf, in-game location]
  • A. in-universe location chosen
    An in-universe location is a specific place within a fictional setting where events occur and characters interact, defined by its unique geography, culture, and narrative significance.
  • B. location-based game
    A location-based game is an interactive digital or physical game whose mechanics and progression depend on the player’s real-world geographic position, often tracked via GPS or similar technologies.
  • C. 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.
  • D. location in The Elder Scrolls
    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.
  • E. location in the Sonic the Hedgehog series
    A location in the Sonic the Hedgehog series represents any distinct place or environment within the Sonic universe, such as zones, cities, or landmarks, where gameplay, story events, or character interactions occur.
  • 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_69f76ec2af148190897d101070d7f415 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:17 p.m.