Triple

T28070240
Position Surface form Disambiguated ID Type / Status
Subject New Preston, Connecticut E709374 entity
Predicate roadAccess P385 FINISHED
Object Connecticut Route 202
Connecticut Route 202 is a segment of the U.S. Route 202 corridor in Connecticut, serving as a key east–west arterial highway connecting numerous towns across the state.
E1930123 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: Connecticut Route 202 | Statement: [New Preston, Connecticut, roadAccess, Connecticut Route 202]
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: Connecticut Route 202
Triple: [New Preston, Connecticut, roadAccess, Connecticut Route 202]
Generated description
Connecticut Route 202 is a segment of the U.S. Route 202 corridor in Connecticut, serving as a key east–west arterial highway connecting numerous towns across the state.

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_69ef9b6f8078819098b741274cd1a2ee completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f6401f19f481909e5e0ea3b2269bbe completed May 2, 2026, 6:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28b063bc208190b08b552674f6079b completed June 10, 2026, 12:31 a.m.
NEDg Description generation batch_6a28b1224e988190aaf3098abf9b89d7 completed June 10, 2026, 12:34 a.m.
NED2 Entity disambiguation (via description) batch_6a28b1d59c0881909073de8cceebb293 completed June 10, 2026, 12:37 a.m.
Created at: April 27, 2026, 8:45 p.m.