Triple

T15206252
Position Surface form Disambiguated ID Type / Status
Subject Interstate 335 E363396 entity
Predicate signedAs P11811 FINISHED
Object I-335 E499320 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-335 | Statement: [Interstate 335, signedAs, I-335]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: I-335
Context triple: [Interstate 335, signedAs, I-335]
  • A. I-335 chosen
    I-335 is a segment of the Kansas Turnpike that forms part of the Interstate Highway System, connecting Emporia and Topeka in eastern Kansas.
  • B. I-235
    I-235 is an auxiliary Interstate Highway that serves as a bypass route around Wichita, Kansas.
  • C. I-375
    I-375 is a short auxiliary Interstate Highway in downtown Detroit, Michigan, connecting I-75 to the city's central business district and riverfront.
  • 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-24
    I-24 is a major east–west Interstate Highway in the United States that runs through states including Tennessee and Kentucky, connecting the Nashville and Chattanooga areas with southern Illinois.
  • 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e006b7964c8190bc8dc3444b94f15e completed April 15, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69fed33dbda08190a10ba81082d0d183 completed May 9, 2026, 6:25 a.m.
Created at: April 10, 2026, 3:11 a.m.