Triple
T29795162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulthar |
E756524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in the Dreamlands |
C56934
|
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: location in the Dreamlands Context triple: [Ulthar, instanceOf, location in the Dreamlands]
-
A.
location in Discworld
A location in Discworld is any distinct place—such as a city, region, landmark, or realm—within Terry Pratchett’s Discworld universe, characterized by its unique geography, culture, inhabitants, and narrative significance.
-
B.
location in the Foundation universe
A "location in the Foundation universe" represents any distinct physical or spatial setting—such as planets, space stations, sectors, or regions—within the fictional cosmos of Isaac Asimov’s Foundation series, characterized by its geography, political affiliation, culture, and narrative significance.
-
C.
location in the Discworld series
A location in the Discworld series is any distinct place—such as a city, region, landmark, or realm—within Terry Pratchett’s flat, disc-shaped world that serves as a setting for events, cultures, and characters in the novels.
-
D.
مكان خيالي
مكان خيالي هو فضاء غير واقعي من صنع الخيال البشري، تُنسَج فيه الأحداث والشخصيات والقوانين بعيدًا عن قيود العالم الحقيقي.
-
E.
location in the Diablo universe
A location in the Diablo universe is any distinct, lore-rich place—such as towns, dungeons, wilderness areas, or realms—where characters can explore, battle enemies, and experience story events within Sanctuary and its connected planes.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:14 p.m.