Triple

T11998770
Position Surface form Disambiguated ID Type / Status
Subject Connecticut Route 275 E285600 entity
Predicate abbreviation P43 FINISHED
Object Route 275 E955812 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: Route 275 | Statement: [Connecticut Route 275, abbreviation, Route 275]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 275
Context triple: [Connecticut Route 275, abbreviation, Route 275]
  • A. Route 275 chosen
    Route 275 is a state highway in Connecticut that serves as a short connector route in the eastern part of the state.
  • B. Route 254
    Route 254 is a state highway in Connecticut that serves as a connector route through Litchfield County, linking several local communities and major roads.
  • C. Route 175
    Route 175 is a major north–south highway in Quebec that connects the Quebec City region to the Saguenay–Lac-Saint-Jean area through the Laurentian Wildlife Reserve.
  • D. Route 752
    Route 752 is a short state highway located in St. Joseph, Missouri.
  • E. Route 220
    Route 220 is a regional highway on Newfoundland’s Burin Peninsula that connects several coastal communities and serves as a primary transportation corridor in the area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ab44a77c8190a652f4b27164e4ef completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903c26d7881909b67a31d04882eb5 completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f640b9a481908de1b7858e3db52c completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:46 p.m.