Triple

T21374495
Position Surface form Disambiguated ID Type / Status
Subject Interstate 380 E527161 entity
Predicate abbreviation P43 FINISHED
Object I-380 NE NERFINISHED

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-380 | Statement: [Interstate 380, abbreviation, I-380]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: I-380
Context triple: [Interstate 380, abbreviation, I-380]
  • A. Interstate 380
    Interstate 380 is a major north–south auxiliary Interstate Highway in eastern Iowa that connects Interstate 80 near Iowa City to Waterloo.
  • B. Interstate 380
    Interstate 380 is a limited-access highway in northeastern Pennsylvania that connects the Scranton area with Interstate 80 and serves as a key regional transportation corridor.
  • C. Interstate 380
    Interstate 380 is a short auxiliary Interstate Highway in the San Francisco Bay Area that connects Interstate 280 to U.S. Route 101 near San Francisco International Airport.
  • D. I-376
    I-376 is an Interstate Highway in western Pennsylvania that connects Pittsburgh to its international airport and the Pennsylvania Turnpike.
  • E. I-335
    I-335 is a segment of the Kansas Turnpike that forms part of the Interstate Highway System, connecting Emporia and Topeka in eastern Kansas.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

Provenance (2 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_69e0b51e80808190ba5cb05667af02a9 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0b3666c8190a83bb32eeba24105 completed April 22, 2026, 11:27 a.m.
Created at: April 16, 2026, 5:10 p.m.