Triple

T19939218
Position Surface form Disambiguated ID Type / Status
Subject Interstate 678 E479258 entity
Predicate alsoKnownAs P39 FINISHED
Object I-678 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-678 | Statement: [Interstate 678, alsoKnownAs, I-678]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: I-678
Context triple: [Interstate 678, alsoKnownAs, I-678]
  • A. I-678 chosen
    I-678, also known as the Van Wyck Expressway, is a major Interstate highway in New York City that links John F. Kennedy International Airport with the Whitestone Expressway and the Bronx–Whitestone Bridge.
  • B. I-640
    I-640 is an auxiliary Interstate Highway that serves as a bypass route around Knoxville, Tennessee.
  • C. I-664
    I-664 is an Interstate highway in southeastern Virginia that serves as a major north–south bypass route around the Hampton Roads region.
  • D. I-196
    I-196 is an auxiliary Interstate Highway in Michigan that connects the Grand Rapids area to the Lake Michigan shoreline and the city of Holland.
  • E. I-184
    I-184 is a short auxiliary Interstate Highway in Boise, Idaho, connecting Interstate 84 with the city's downtown area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8e522a17c819095165d4d24939fd8 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65a19d77c819088bce99c94568d0d completed April 20, 2026, 4:53 p.m.
Created at: April 10, 2026, 1:53 p.m.