Triple
T26827996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morwen Eledhwen |
E675421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Character in the legendarium of J. R. R. Tolkien |
C11450
|
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: Character in the legendarium of J. R. R. Tolkien Context triple: [Morwen Eledhwen, instanceOf, Character in the legendarium of J. R. R. Tolkien]
-
A.
Middle-earth character
chosen
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.
-
B.
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.
-
C.
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.
-
D.
group of characters in Middle-earth
A group of characters in Middle-earth is a collection of individuals—such as Hobbits, Elves, Dwarves, Men, or other beings—who are connected by shared purpose, lineage, culture, or circumstance within Tolkien’s fictional world.
-
E.
member of the Fellowship of the Ring
A member of the Fellowship of the Ring is an individual chosen to join the nine-person company tasked with aiding and protecting Frodo Baggins on his quest to destroy the One Ring in the fires of Mount Doom.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 4:59 a.m.