Triple

T9652242
Position Surface form Disambiguated ID Type / Status
Subject I-110 (Florida) E233362 entity
Predicate abbreviation P43 FINISHED
Object I-110 E233362 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-110 | Statement: [I-110 (Florida), abbreviation, I-110]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I-110
Context triple: [I-110 (Florida), abbreviation, I-110]
  • A. I-110 chosen
    I-110 is a short auxiliary Interstate Highway in Florida that connects downtown Pensacola to Interstate 10.
  • B. I-190
    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.
  • C. I-485
    I-485 is the beltway interstate highway that loops around the city of Charlotte, North Carolina.
  • D. I-229
    I-229 is a short auxiliary Interstate Highway in Missouri that serves as a bypass and business route around downtown St. Joseph.
  • E. I-229
    I-229 is an auxiliary Interstate Highway that serves as a bypass route around Sioux Falls in southeastern South Dakota.
  • 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_69ca848b31648190b57aa55da20285be completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9bb0cce88190b7eacc8b43450d7f completed April 1, 2026, 10:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1826c91388190b82112c2ca1eae7e completed April 4, 2026, 9:28 p.m.
Created at: March 30, 2026, 8:13 p.m.