Triple

T28666756
Position Surface form Disambiguated ID Type / Status
Subject Macroverse E725604 entity
Predicate relatedTo P37 FINISHED
Object Todash darkness
Todash darkness is a mysterious, terrifying void-like dimension in Stephen King’s multiverse, associated with the spaces between worlds and inhabited by monstrous entities.
E1828380 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Todash darkness | Statement: [Macroverse, relatedTo, Todash darkness]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Todash darkness
Triple: [Macroverse, relatedTo, Todash darkness]
Generated description
Todash darkness is a mysterious, terrifying void-like dimension in Stephen King’s multiverse, associated with the spaces between worlds and inhabited by monstrous entities.

Provenance (5 batches)

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_69f01d85be388190b669a0e401e2f2c4 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f655a504a88190a43d5a48ebbc6a4a completed May 2, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1cc395a1a88190877ee0a155d4b3eb completed May 31, 2026, 11:26 p.m.
NEDg Description generation batch_6a1cc463bda48190bec84f370b367cff completed May 31, 2026, 11:29 p.m.
NED2 Entity disambiguation (via description) batch_6a1cc5027a4881908055cfa03af83b64 completed May 31, 2026, 11:32 p.m.
Created at: April 28, 2026, 5:01 a.m.