Triple

T21362240
Position Surface form Disambiguated ID Type / Status
Subject State Route 28 (Washington) E526811 entity
Predicate abbreviation P43 FINISHED
Object SR 28 NE NERFINISHED

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 28 | Statement: [State Route 28 (Washington), abbreviation, SR 28]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 28
Context triple: [State Route 28 (Washington), abbreviation, SR 28]
  • A. SR 28
    SR 28 is a primary state highway in Virginia that serves as a major north–south transportation corridor in the northern part of the state.
  • B. SR 28
    SR 28 is a scenic Nevada state highway that runs along the northeastern shore of Lake Tahoe, connecting U.S. Route 50 near Spooner Lake to the California state line.
  • C. SR 28 chosen
    SR 28 is a state highway in Washington that runs through central and eastern parts of the state, connecting communities along the Columbia River.
  • D. SR 282
    SR 282 is a short state highway in Maine that connects the town of Old Orchard Beach with nearby routes and communities.
  • E. SR 280
    SR 280 is a state highway in Maine that serves as a regional connector route within the state's road network.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b51d8a308190b09113b3b3f9bc15 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b06b219c81908f7674ae459e7931 completed April 22, 2026, 11:26 a.m.
Created at: April 16, 2026, 5:08 p.m.