Triple
T37565742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwindor |
E933949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | TolkienLegendariumCharacter |
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: TolkienLegendariumCharacter Context triple: [Gwindor, instanceOf, TolkienLegendariumCharacter]
-
A.
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.
-
B.
entities in Tolkien legendarium
Entities in the Tolkien legendarium are the diverse beings—mortal and immortal, corporeal and incorporeal, natural and supernatural—that inhabit, shape, and are shaped by the mythic world of Arda across its ages.
-
C.
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.
-
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.
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.
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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.