Triple

T16680253
Position Surface form Disambiguated ID Type / Status
Subject Alabama State Route 119 E405319 entity
Predicate abbreviation P43 FINISHED
Object SR 119 E843132 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 119 | Statement: [Alabama State Route 119, abbreviation, SR 119]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SR 119
Context triple: [Alabama State Route 119, abbreviation, SR 119]
  • A. SR 119 chosen
    SR 119 is a state highway in Alabama that serves as a regional connector route through several suburban and rural communities.
  • B. SR 189
    SR 189 is a state highway in eastern Maine that connects the town of Whiting to the coastal community of Lubec near the Canadian border.
  • C. SR 191
    SR 191 is a state highway in Maine that runs through Washington County, connecting coastal and inland communities.
  • D. SR 111
    SR 111 is a state highway in Maine that runs east–west, connecting the city of Biddeford to the town of Alfred and serving as an important regional route in York County.
  • E. SR 111
    SR 111 is a major north–south state highway in Southern California that runs through the Coachella and Imperial Valleys, connecting desert communities and serving as a key regional route.
  • 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_69d8838c28748190b3f5967c743940ab completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37d6e74ec81909ea95c3e4b0113ab completed April 18, 2026, 12:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a009194ad188190aae3371c97abc045 completed May 10, 2026, 2:09 p.m.
Created at: April 10, 2026, 5:19 a.m.