Triple

T1497410
Position Surface form Disambiguated ID Type / Status
Subject I-355 E29716 entity
Predicate abbreviation P43 FINISHED
Object I-355 E393863 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: I-355 | Statement: [I-355, abbreviation, I-355]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I-355
Context triple: [I-355, abbreviation, I-355]
  • A. Interstate 355 chosen
    Interstate 355 is a toll highway in the Chicago metropolitan area that serves as a suburban north–south bypass around the city.
  • B. Interstate 35E
    Interstate 35E is the eastern branch of Interstate 35 that runs through Dallas, Texas, serving as a key north–south transportation corridor in the region.
  • C. Interstate 35E
    Interstate 35E is a major north–south U.S. Interstate Highway that runs through Saint Paul, Minnesota, as part of the split of Interstate 35 in the Twin Cities metropolitan area.
  • D. Interstate 35
    Interstate 35 is a major north–south U.S. highway running from the Mexican border in Texas through the central United States to Minnesota, serving numerous key cities along its route.
  • E. Interstate 293
    Interstate 293 is a short auxiliary Interstate highway that forms a partial beltway around Manchester, New Hampshire, connecting Interstate 93 with other major routes in the 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_69a498dba1d8819093b46a3a8d2485f1 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6edca248190a90205799b270058 completed March 1, 2026, 11:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5a80f97f88190b502bca0547f03a0 completed March 14, 2026, 6:25 p.m.
Created at: March 1, 2026, 8:12 p.m.