Triple

T16627528
Position Surface form Disambiguated ID Type / Status
Subject California State Route 17 E403987 entity
Predicate abbreviation P43 FINISHED
Object SR 17 E908504 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 17 | Statement: [California State Route 17, abbreviation, SR 17]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 17
Context triple: [California State Route 17, abbreviation, SR 17]
  • A. SR 17 chosen
    SR 17 is a heavily traveled and winding state highway in California that connects San Jose in Silicon Valley with the city of Santa Cruz across the Santa Cruz Mountains.
  • B. SR 17
    SR 17 is a state highway in Washington that runs through central and eastern parts of the state, connecting communities in the Columbia Basin and serving as a key regional transportation corridor.
  • C. SR 171
    SR 171 is a state highway in Maine that serves as a local connector route within the state's road network.
  • D. SR 171
    SR 171 is a short state highway in central Washington that connects the city of Moses Lake to nearby rural areas and other regional routes.
  • E. SR 170
    SR 170 is a state highway in Maine that serves as a regional connector route through rural parts of the state.
  • 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_69d883897eb481909eaaa088ba9918d9 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e378e2683481908c9a5ed895a09a6e completed April 18, 2026, 12:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084b7b94481909dfc0dd7b009a5b4 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:17 a.m.