Triple

T5170593
Position Surface form Disambiguated ID Type / Status
Subject I-435 E116666 entity
Predicate connectsTo P845 FINISHED
Object I-35 E20699 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-35 | Statement: [I-435, connectsTo, I-35]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I-35
Context triple: [I-435, connectsTo, I-35]
  • A. Interstate 35 chosen
    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.
  • 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 355
    Interstate 355 is a toll highway in the Chicago metropolitan area that serves as a suburban north–south bypass around the city.
  • E. Interstate 30
    Interstate 30 is a major east–west U.S. highway running through Texas and Arkansas, connecting cities such as Dallas and Fort Worth to Little Rock.
  • 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_69bd445ff97c81909a2615cc56235470 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd794f44248190a3a90c92208104a7 completed March 20, 2026, 4:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c98bd7f4dc8190975352b1eb790cae completed March 29, 2026, 8:30 p.m.
Created at: March 20, 2026, 1:45 p.m.