Triple
T33624643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Eärendil |
E861369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tolkien legendarium concept |
C26228
|
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: Tolkien legendarium concept Context triple: [House of Eärendil, instanceOf, Tolkien legendarium concept]
-
A.
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.
-
B.
conflict in Tolkien legendarium
Conflict in the Tolkien legendarium is the dynamic interplay of moral, cultural, and cosmic oppositions—often embodied in wars, quests, and inner struggles—that shape the fate of Middle-earth and reveal the consequences of power, pride, and mercy.
-
C.
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.
-
D.
character group in Tolkien legendarium
chosen
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.
-
E.
object in Tolkien legendarium
An object in the Tolkien legendarium is any physical or crafted item—mundane or magical—that exists within Tolkien’s fictional world and can be used, possessed, or referenced by its characters.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.