Triple
T37037869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Treason of Isengard |
E916696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle-earth scholarship |
C64503
|
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 scholarship Context triple: [The Treason of Isengard, instanceOf, Middle-earth scholarship]
-
A.
Middle-earth canon classification
A system for categorizing and organizing works, characters, events, and lore related to Middle-earth according to their canonical status within Tolkien’s legendarium and its adaptations.
-
B.
Character in the works of J. R. R. Tolkien
A Character in the works of J. R. R. Tolkien is an individual—whether human, hobbit, elf, dwarf, or other being—who inhabits Middle-earth or its related realms, possessing distinct traits, histories, and roles that contribute to the unfolding of Tolkien’s legendarium.
-
C.
doctrine in Tolkien legendarium
A doctrine in the Tolkien legendarium is a coherent set of beliefs, principles, or teachings—often religious, moral, or metaphysical—that shapes the worldview, laws, and practices of peoples and cultures within Middle-earth and beyond.
-
D.
Tolkien scholar
A Tolkien scholar is an expert who studies, analyzes, and interprets the works, languages, mythology, and influences of J.R.R. Tolkien within their literary and historical contexts.
-
E.
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.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.