Triple

T8274569
Position Surface form Disambiguated ID Type / Status
Subject Interstate 405 in Oregon E193509 entity
Predicate routeNumber P1864 FINISHED
Object I-405 E312826 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-405 | Statement: [Interstate 405 in Oregon, routeNumber, I-405]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I-405
Context triple: [Interstate 405 in Oregon, routeNumber, I-405]
  • A. I-405 chosen
    I-405 is a major auxiliary Interstate Highway that serves as a heavily traveled bypass and commuter route around parts of the greater Los Angeles and Seattle metropolitan areas.
  • B. I-235
    I-235 is an auxiliary Interstate Highway that serves as a bypass route around Wichita, Kansas.
  • C. I-4
    I-4 is a major east–west Interstate Highway in Florida that connects Tampa, Orlando, and Daytona Beach.
  • D. I-278
    I-278 is a major auxiliary Interstate Highway in New York City that connects several boroughs via routes such as the Bruckner, Brooklyn-Queens, and Staten Island expressways.
  • E. I-84
    I-84 is a major east–west Interstate Highway in the northwestern United States, running through Oregon and Idaho as a key regional transportation corridor.
  • 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_69ca82e14ae481908ffdb822cd2192bc completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb798bc29c8190927ef4b0662d6b98 completed March 31, 2026, 7:36 a.m.
NED1 Entity disambiguation (via context triple) batch_69cdc6ca48308190bd7a6c84d5954279 completed April 2, 2026, 1:30 a.m.
Created at: March 30, 2026, 5:51 p.m.