Triple
T11046858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventures of Tom Bombadil |
E261157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle-earth legendarium work |
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 legendarium work Context triple: [The Adventures of Tom Bombadil, instanceOf, Middle-earth legendarium work]
-
A.
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.
-
B.
language of Middle-earth
The language of Middle-earth is a richly constructed set of tongues, scripts, and linguistic histories created by J.R.R. Tolkien to give depth, culture, and realism to the peoples and stories of his fictional world.
-
C.
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.
-
D.
region of Middle-earth
A region of Middle-earth is a geographically defined area within Tolkien’s fictional world, characterized by its distinct landscapes, cultures, histories, and roles in the overarching narrative.
-
E.
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.
- F. None of above. chosen
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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.