Triple

T24120945
Position Surface form Disambiguated ID Type / Status
Subject Rich County, Utah E597649 entity
Predicate hasDST P384 FINISHED
Object Mountain Daylight Time
Mountain Daylight Time is the daylight saving time zone used in parts of North America, including much of the Mountain Time Zone region, during the summer months.
E110191 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: Mountain Daylight Time | Statement: [Rich County, Utah, hasDST, Mountain Daylight Time]
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: Mountain Daylight Time
Triple: [Rich County, Utah, hasDST, Mountain Daylight Time]
Generated description
Mountain Daylight Time is the daylight saving time zone used in parts of North America, including much of the Mountain Time Zone region, during the summer months.

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_69e288c74200819098ab875b592cb39f completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1dee2defc81909df55900769fef5b completed April 29, 2026, 10:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f9689dec08190945799440ef1d65e completed May 21, 2026, 11:34 p.m.
NEDg Description generation batch_6a0f982c5d5c8190a3c45f24be668438 completed May 21, 2026, 11:41 p.m.
NED2 Entity disambiguation (via description) batch_6a0f9858184c8190af6293dbf5c3c963 completed May 21, 2026, 11:42 p.m.
Created at: April 17, 2026, 11:05 p.m.