Triple

T38415661
Position Surface form Disambiguated ID Type / Status
Subject Utah State Route 128 E901593 entity
Predicate partOf P40 FINISHED
Object Utah Scenic Byway 128
Utah Scenic Byway 128 is a renowned scenic highway in eastern Utah that follows the Colorado River through dramatic red rock canyons between Moab and Interstate 70.
E2270216 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: Utah Scenic Byway 128 | Statement: [Utah State Route 128, partOf, Utah Scenic Byway 128]
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: Utah Scenic Byway 128
Triple: [Utah State Route 128, partOf, Utah Scenic Byway 128]
Generated description
Utah Scenic Byway 128 is a renowned scenic highway in eastern Utah that follows the Colorado River through dramatic red rock canyons between Moab and Interstate 70.

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_69f76e61e79c81908b787d83b46ab92b completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fccd82530c81909f8d232f60da676d completed May 7, 2026, 5:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41c285f8cc819091786c8d88e651f0 completed June 29, 2026, 12:55 a.m.
NEDg Description generation batch_6a41c38d00308190aa8cbf6fbc9f081b completed June 29, 2026, 12:59 a.m.
NED2 Entity disambiguation (via description) batch_6a41c76fae84819094a9930a06e8ce2f completed June 29, 2026, 1:16 a.m.
Created at: May 3, 2026, 4:31 p.m.