Triple

T18550310
Position Surface form Disambiguated ID Type / Status
Subject Soddy-Daisy, Tennessee E453355 entity
Predicate hasTransportation P105 FINISHED
Object Tennessee State Route 319 — 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: Tennessee State Route 319 | Statement: [Soddy-Daisy, Tennessee, hasTransportation, Tennessee State Route 319]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Tennessee State Route 319
Context triple: [Soddy-Daisy, Tennessee, hasTransportation, Tennessee State Route 319]
  • A. Tennessee State Route 334
    Tennessee State Route 334 is a short state highway in Blount County that serves as a connector route through and around the town of Louisville, Tennessee.
  • B. Tennessee State Route 338
    Tennessee State Route 338 is a state highway in Tennessee that serves the Seymour area, providing a local connector route within Sevier County.
  • C. Tennessee State Route 330
    Tennessee State Route 330 is a short state highway in Tennessee that serves as a local connector route in Anderson County, linking rural communities to the broader state road network.
  • D. Tennessee State Route 323
    Tennessee State Route 323 is a short state highway in eastern Tennessee that connects the town of Philadelphia to nearby Interstate and regional routes.
  • E. Tennessee State Route 340
    Tennessee State Route 340 is a secondary state highway in eastern Tennessee that serves as a local connector between rural communities and other regional routes.
  • 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: Tennessee State Route 319
Target entity description: Tennessee State Route 319 is a state highway in Tennessee that serves the Chattanooga metropolitan area, including the city of Soddy-Daisy, providing a local connector route for regional traffic.
  • A. Tennessee State Route 334
    Tennessee State Route 334 is a short state highway in Blount County that serves as a connector route through and around the town of Louisville, Tennessee.
  • B. Tennessee State Route 338
    Tennessee State Route 338 is a state highway in Tennessee that serves the Seymour area, providing a local connector route within Sevier County.
  • C. Tennessee State Route 330
    Tennessee State Route 330 is a short state highway in Tennessee that serves as a local connector route in Anderson County, linking rural communities to the broader state road network.
  • D. Tennessee State Route 323
    Tennessee State Route 323 is a short state highway in eastern Tennessee that connects the town of Philadelphia to nearby Interstate and regional routes.
  • E. Tennessee State Route 340
    Tennessee State Route 340 is a secondary state highway in eastern Tennessee that serves as a local connector between rural communities and other regional routes.
  • 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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53800c0fc819097782f1e81574598 completed April 19, 2026, 8:16 p.m.
Created at: April 10, 2026, 11:38 a.m.