Triple
T35137970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great War |
E1014624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict in The Elder Scrolls |
C61880
|
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: conflict in The Elder Scrolls Context triple: [Great War, instanceOf, conflict in The Elder Scrolls]
-
A.
event in The Elder Scrolls universe
chosen
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.
conflict in video game
Conflict in a video game is the central struggle or opposition—between players, characters, or forces—that drives gameplay challenges, narrative tension, and player engagement.
-
C.
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.
-
D.
clan conflict
A clan conflict is a prolonged, often intergenerational struggle between kin-based groups driven by competition over resources, power, honor, or historical grievances.
-
E.
conflict in Tolkien legendarium
Conflict in the Tolkien legendarium is the dynamic interplay of moral, cultural, and cosmic oppositions—often embodied in wars, quests, and inner struggles—that shape the fate of Middle-earth and reveal the consequences of power, pride, and mercy.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.