Triple
T38590525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limsa Lominsa |
E932442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Final Fantasy XIV |
C66170
|
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 Final Fantasy XIV Context triple: [Limsa Lominsa, instanceOf, location in Final Fantasy XIV]
-
A.
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.
-
B.
location in Warcraft universe
A location in the Warcraft universe is any distinct, named place—such as a city, region, dungeon, or landmark—within Azeroth or its connected realms that provides geographical context, lore significance, and gameplay functions.
-
C.
location in Maldraxxus
A location in Maldraxxus is a distinct area or landmark within the necromantic war-torn realm of Maldraxxus, characterized by its martial purpose, grotesque aesthetics, and role in the Shadowlands’ defense.
-
D.
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.
-
E.
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.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.