Triple
T35051069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Era |
E1011330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | time period in The Elder Scrolls universe |
C2774
|
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: time period in The Elder Scrolls universe Context triple: [Third Era, instanceOf, time period in The Elder Scrolls universe]
-
A.
event in The Elder Scrolls universe
An event in The Elder Scrolls universe is a significant occurrence—such as a battle, prophecy fulfillment, political upheaval, or divine intervention—that shapes the history, cultures, and power dynamics of Tamriel and its surrounding realms.
-
B.
time period
chosen
A time period is a continuous span of time defined by specific start and end points, often characterized by particular events, conditions, or properties.
-
C.
age of Middle-earth
The age of Middle-earth is a period in J.R.R. Tolkien’s legendarium marked by the unfolding histories, cultures, and conflicts of its races and realms across successive epochs such as the First, Second, and Third Ages.
-
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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.