Triple

T20421016
Position Surface form Disambiguated ID Type / Status
Subject Connecticut Route 302 E500848 entity
Predicate easternTerminus P388 FINISHED
Object U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut — NE NERFINISHED

How this triple was built (3 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: U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut | Statement: [Connecticut Route 302, easternTerminus, U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut
Context triple: [Connecticut Route 302, easternTerminus, U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut]
  • A. Connecticut Route 66
    Connecticut Route 66 is an east–west state highway in central and eastern Connecticut that connects several towns and cities, serving as a key regional arterial route.
  • B. Connecticut Route 67
    Connecticut Route 67 is a state highway in western Connecticut that connects several towns, including Oxford, and serves as a key regional route for local and commuter traffic.
  • C. Connecticut Route 68
    Connecticut Route 68 is a state highway in central Connecticut that connects several towns, including Naugatuck, Prospect, and Wallingford, serving as an important east–west commuter and local access route.
  • D. Connecticut Route 69
    Connecticut Route 69 is a north–south state highway in Connecticut that connects the New Haven area with inland communities including Wolcott and beyond.
  • E. Connecticut Route 63
    Connecticut Route 63 is a state highway in Connecticut that runs generally north–south, connecting New Haven to the Litchfield Hills region and serving numerous towns along its route.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut
Target entity description: U.S. Route 6 and U.S. Route 202 in Bethel, Connecticut, form a shared highway corridor that serves as a key regional thoroughfare connecting the town to other parts of Fairfield County and beyond.
  • A. Connecticut Route 66
    Connecticut Route 66 is an east–west state highway in central and eastern Connecticut that connects several towns and cities, serving as a key regional arterial route.
  • B. Connecticut Route 67
    Connecticut Route 67 is a state highway in western Connecticut that connects several towns, including Oxford, and serves as a key regional route for local and commuter traffic.
  • C. Connecticut Route 68
    Connecticut Route 68 is a state highway in central Connecticut that connects several towns, including Naugatuck, Prospect, and Wallingford, serving as an important east–west commuter and local access route.
  • D. Connecticut Route 69
    Connecticut Route 69 is a north–south state highway in Connecticut that connects the New Haven area with inland communities including Wolcott and beyond.
  • E. Connecticut Route 63
    Connecticut Route 63 is a state highway in Connecticut that runs generally north–south, connecting New Haven to the Litchfield Hills region and serving numerous towns along its route.
  • F. None of above. chosen

Provenance (2 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_69e0b4aa68fc8190b1a14c55575ef04a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67ba479008190bf6d31ee79f3a401 completed April 20, 2026, 7:16 p.m.
Created at: April 16, 2026, 11:30 a.m.