Triple
T27554139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cirion and Eorl and the Friendship of Gondor and Rohan |
E695588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle-earth legend |
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: Middle-earth legend Context triple: [Cirion and Eorl and the Friendship of Gondor and Rohan, instanceOf, Middle-earth legend]
-
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.
Middle-earth character
A Middle-earth character is a fictional being—such as a human, hobbit, elf, dwarf, or other creature—who inhabits J.R.R. Tolkien’s legendarium and participates in its mythic histories and adventures.
-
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.
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.
event in Middle-earth legendarium
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.
- 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.