Triple
T37094344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Realms of Arnor and Gondor |
E918518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subject of J. R. R. Tolkien |
C29887
|
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: subject of J. R. R. Tolkien Context triple: [Realms of Arnor and Gondor, instanceOf, subject of J. R. R. Tolkien]
-
A.
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.
-
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.
Middle-earth scholarship
Middle-earth scholarship is the academic and critical study of J.R.R. Tolkien’s invented world, examining its languages, histories, cultures, themes, and literary influences.
-
D.
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.
-
E.
place in J. R. R. Tolkien's legendarium
chosen
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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.