Triple

T12238335
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 160 E291660 entity
Predicate abbreviation P43 FINISHED
Object SR 160 E841293 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: SR 160 | Statement: [Maine State Route 160, abbreviation, SR 160]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SR 160
Context triple: [Maine State Route 160, abbreviation, SR 160]
  • A. SR 160 chosen
    SR 160 is a Nevada state highway that connects Las Vegas to Pahrump and serves as a major route through the Spring Mountains region.
  • B. SR 16
    SR 16 is a state highway in Maine that runs east–west across the central and western parts of the state, connecting several rural communities and major routes.
  • C. SR 16
    SR 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
  • D. SR 16
    SR 16 is a primary state highway in Washington that connects the Tacoma area to the Kitsap Peninsula, including the Tacoma Narrows Bridge crossing.
  • E. SR 168
    SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
  • 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_69d6ab668acc8190963ba424049d6aee completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cb45340819093365f8efdf85f75 completed April 10, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64b893a70819090d4ebb0609e6544 completed May 2, 2026, 7:07 p.m.
Created at: April 8, 2026, 9:51 p.m.