Triple
T27554096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Disaster of the Gladden Fields |
E695587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tolkien legendarium element |
C29064
|
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: Tolkien legendarium element Context triple: [The Disaster of the Gladden Fields, instanceOf, Tolkien legendarium element]
-
A.
Middle-earth legendarium work
chosen
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.
-
B.
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.
-
C.
character group in Tolkien legendarium
A character group in the Tolkien legendarium is a collection of individuals—such as races, cultures, or fellowships—united by shared lineage, purpose, or identity within the mythic world of Middle-earth and beyond.
-
D.
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.
-
E.
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.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:36 p.m.