Triple
T32096176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkening of Valinor |
E819727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Tolkien legendarium |
C29074
|
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: event in Tolkien legendarium Context triple: [Darkening of Valinor, instanceOf, event in Tolkien legendarium]
-
A.
event in Middle-earth legendarium
chosen
An event in the Middle-earth legendarium is a significant occurrence—historical, mythic, or personal—that shapes the unfolding narrative, cultures, and destinies of characters and realms within Tolkien’s fictional world.
-
B.
Middle-earth legendarium work
A Middle-earth legendarium work is a narrative or reference text set in J.R.R. Tolkien’s fictional world of Middle-earth, contributing to its histories, cultures, languages, and mythic events.
-
C.
place in J. R. R. Tolkien's legendarium
A place in J. R. R. Tolkien's legendarium is any geographically or cosmologically defined location—such as a land, city, region, realm, or landmark—within the fictional world of Arda and its histories.
-
D.
object in Tolkien legendarium
An object in the Tolkien legendarium is any physical or crafted item—mundane or magical—that exists within Tolkien’s fictional world and can be used, possessed, or referenced by its characters.
-
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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:26 a.m.