Triple

T3553577
Position Surface form Disambiguated ID Type / Status
Subject California State Route 28 E75167 entity
Predicate abbreviation P43 FINISHED
Object SR 28 E236859 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 28 | Statement: [California State Route 28, abbreviation, SR 28]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SR 28
Context triple: [California State Route 28, abbreviation, SR 28]
  • A. SR 28 chosen
    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 269
    SR 269 is a short state highway in Florida that serves local traffic in the state's northern region.
  • C. SR 180
    SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
  • D. SR 27
    SR 27 is a state highway in Maine that runs north–south, connecting coastal communities with inland towns and recreational areas.
  • E. SR 243
    SR 243 is a short primary state highway in Fairfax County, Virginia, serving as a connector route in the suburban Washington, D.C. metropolitan area.
  • 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_69ad85d33c6c819081d5ac1df13b5680 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc05394888190b59fafda97b49beb completed March 8, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb9218448190ae432ae74c0a6916 completed March 13, 2026, 7:24 a.m.
Created at: March 8, 2026, 3:20 p.m.