Triple
T36545797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivers of Middle-earth |
E901137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional geographic feature collection |
C7345
|
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: fictional geographic feature collection Context triple: [Rivers of Middle-earth, instanceOf, fictional geographic feature collection]
-
A.
geographical feature
A geographical feature is a naturally occurring or human-made physical element of the Earth's surface, such as mountains, rivers, valleys, or roads, that can be distinctly identified and described.
-
B.
collection of mythological locations
A collection of mythological locations represents an organized set of legendary places from various myths and folklore traditions, each with its own symbolic meaning, narrative role, and cultural origin.
-
C.
fictional place
chosen
A fictional place is an imagined location or setting created within a narrative work, such as a novel, film, or game, that does not exist in the real world.
-
D.
fictionalized location depiction
A fictionalized location depiction is a representation of a real or imagined place that alters, embellishes, or reinterprets its geography, culture, or atmosphere to serve narrative, thematic, or aesthetic purposes.
-
E.
fictional national park
A fictional national park is an imagined, protected natural area created within a narrative or worldbuilding context, featuring distinctive landscapes, ecosystems, and cultural elements that serve story, thematic, or experiential purposes.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.