Triple

T3133131
Position Surface form Disambiguated ID Type / Status
Subject Interstate 74 E65462 entity
Predicate hasJunctionWith P1018 FINISHED
Object Interstate 465 E527250 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: Interstate 465 | Statement: [Interstate 74, hasJunctionWith, Interstate 465]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Interstate 465
Context triple: [Interstate 74, hasJunctionWith, Interstate 465]
  • A. Interstate 465 chosen
    Interstate 465 is a beltway highway encircling Indianapolis, Indiana, serving as a major connector between the city and its surrounding suburbs and regional highways.
  • B. Interstate 430
    Interstate 430 is a bypass freeway in the Little Rock, Arkansas metropolitan area that connects Interstate 30 with Interstate 40 and helps route traffic around the city.
  • C. Interstate 285
    Interstate 285 is the beltway encircling Atlanta, Georgia, serving as a major bypass and connector for multiple interstate highways around the metropolitan area.
  • D. Interstate 285
    Interstate 285 is a short auxiliary Interstate highway in North Carolina that serves as a connector route near Winston-Salem.
  • E. Interstate 630
    Interstate 630 is an east–west auxiliary Interstate Highway serving as a major commuter route through Little Rock, Arkansas.
  • 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_69ad8581c25c8190b0d85ba9b9baa531 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada56104ec8190a14591ed73f3fe83 completed March 8, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d4f458288190ac1d6a8489bbc943 completed March 27, 2026, 7:05 p.m.
Created at: March 8, 2026, 3:04 p.m.