Triple
T36550709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Túna |
E901249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Tolkien legendarium |
C65776
|
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 Tolkien legendarium Context triple: [Túna, instanceOf, location in Tolkien legendarium]
-
A.
location in Beleriand
chosen
A "location in Beleriand" represents any distinct geographical place—such as a region, city, landmark, or natural feature—within the fictional land of Beleriand in J.R.R. Tolkien’s legendarium.
-
B.
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.
-
C.
location in the world of Game of Thrones
A location in the world of Game of Thrones is any distinct geographical place—such as a city, castle, region, or landmark—within the fictional continents of Westeros and Essos that serves as a setting for events, characters, and political or magical significance.
-
D.
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.
-
E.
structure in Middle-earth
A "structure in Middle-earth" is any constructed or naturally formed edifice—such as towers, fortresses, halls, bridges, or monumental landmarks—located within Tolkien’s fictional world of Middle-earth.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.