Triple

T15404006
Position Surface form Disambiguated ID Type / Status
Subject Interstate 190 (Illinois) E368401 entity
Predicate abbreviation P43 FINISHED
Object I-190 E496612 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-190 | Statement: [Interstate 190 (Illinois), abbreviation, I-190]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I-190
Context triple: [Interstate 190 (Illinois), abbreviation, I-190]
  • A. I-190 chosen
    I-190 is a short auxiliary Interstate Highway in Massachusetts that connects Worcester to the Leominster–Fitchburg area and links to I-290 and Route 2.
  • B. I-229
    I-229 is an auxiliary Interstate Highway that serves as a bypass route around Sioux Falls in southeastern South Dakota.
  • C. I-229
    I-229 is a short auxiliary Interstate Highway in Missouri that serves as a bypass and business route around downtown St. Joseph.
  • D. I-520
    I-520 is an auxiliary Interstate Highway that forms a partial beltway around Augusta, Georgia and North Augusta, South Carolina.
  • E. I-220
    I-220 is an auxiliary Interstate Highway in the United States that serves as a bypass or loop around a primary Interstate route.
  • 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_69d85a16c68c819099c1b547fbc87b32 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e8fde64819082ec0c68df305561 completed April 16, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff135a26f08190ad3fc1d5a263a24e completed May 9, 2026, 10:58 a.m.
Created at: April 10, 2026, 3:19 a.m.