Triple

T17787293
Position Surface form Disambiguated ID Type / Status
Subject State Route 57 E444050 entity
Predicate abbreviation P43 FINISHED
Object SR 57 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 57 | Statement: [State Route 57, abbreviation, SR 57]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 57
Context triple: [State Route 57, abbreviation, SR 57]
  • A. SR 57 chosen
    SR 57 is a major north–south state highway in Southern California that connects Orange County to the Pomona area and serves as a key commuter and freight corridor.
  • B. SR 57
    SR 57 is a state highway in Ohio that serves as a regional connector route through several communities in the northern part of the state.
  • C. SR 55
    SR 55 is a state highway in Georgia that serves as a regional connector route through several counties in the state.
  • D. SR 51
    SR 51 is a major north–south freeway in the Phoenix, Arizona metropolitan area that connects downtown Phoenix with its northeastern suburbs.
  • E. SR 58
    SR 58 is a major east–west California state highway that connects the Central Coast to the Mojave Desert, serving as an important freight and travel corridor across the state.
  • 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_69d8b9ef17708190bdf7e2adbf14ddc2 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48794542c8190b049bce6e28c9f3a completed April 19, 2026, 7:43 a.m.
Created at: April 10, 2026, 10:12 a.m.