Triple

T14066283
Position Surface form Disambiguated ID Type / Status
Subject Texas State Highway 183 E338480 entity
Predicate abbreviation P43 FINISHED
Object SH 183 E601973 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: SH 183 | Statement: [Texas State Highway 183, abbreviation, SH 183]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SH 183
Context triple: [Texas State Highway 183, abbreviation, SH 183]
  • A. SH 183 chosen
    SH 183 is a major Texas state highway serving the Dallas–Fort Worth metropolitan area, providing an important east–west transportation corridor.
  • B. SH 121
    SH 121 is a major Texas state highway that serves as a key north–south and northeast–southwest transportation corridor through the Dallas–Fort Worth metropolitan area.
  • C. SH 121
    SH 121 is a state highway in Colorado that runs through the Denver metropolitan area, serving as a major north–south arterial route.
  • D. SH 171
    SH 171 is a Texas state highway that runs through north-central Texas, connecting several rural communities and regional routes.
  • E. SH 152
    SH 152 is a Texas state highway that runs across the Texas Panhandle, connecting the cities of Dumas and Pampa and serving as an important east–west route in the region.
  • 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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de568b81f08190a571004261c0e8e4 completed April 14, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb669111081909ccd167f41571a00 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:21 p.m.