Triple

T15083312
Position Surface form Disambiguated ID Type / Status
Subject Interstate 635 E360205 entity
Predicate abbreviation P43 FINISHED
Object I-635 E783025 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-635 | Statement: [Interstate 635, abbreviation, I-635]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: I-635
Context triple: [Interstate 635, abbreviation, I-635]
  • A. I-635 chosen
    I-635 is an auxiliary Interstate Highway that serves as a major beltway and bypass route around parts of the Dallas–Fort Worth metropolitan area in Texas.
  • B. I-675
    I-675 is a short auxiliary Interstate Highway in the United States that serves as a bypass and connector route around a major metropolitan area.
  • C. I-696
    I-696 is an east–west interstate highway in the Detroit metropolitan area of Michigan, serving as a key commuter and bypass route through suburbs including Southfield.
  • D. 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.
  • E. I-375
    I-375 is a short auxiliary Interstate Highway in downtown Detroit, Michigan, connecting I-75 to the city's central business district and riverfront.
  • 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0027450a48190a84588b6aaf84ebf completed April 15, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69feae179a24819097019976707c93e1 completed May 9, 2026, 3:46 a.m.
Created at: April 10, 2026, 3:03 a.m.