Triple

T587285
Position Surface form Disambiguated ID Type / Status
Subject Duluth E15185 entity
Predicate servedBy P82 FINISHED
Object Interstate 35 E20699 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 35 | Statement: [Duluth, servedBy, Interstate 35]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Interstate 35
Context triple: [Duluth, servedBy, Interstate 35]
  • A. Interstate 35 chosen
    Interstate 35 is a major north–south U.S. highway running from the Mexican border in Texas through the central United States to Minnesota, serving numerous key cities along its route.
  • B. Interstate 35E
    Interstate 35E is the eastern branch of Interstate 35 that runs through Dallas, Texas, serving as a key north–south transportation corridor in the region.
  • C. Interstate 35E
    Interstate 35E is a major north–south U.S. Interstate Highway that runs through Saint Paul, Minnesota, as part of the split of Interstate 35 in the Twin Cities metropolitan area.
  • D. Interstate 29
    Interstate 29 is a major north–south U.S. highway running through the Great Plains from Missouri to North Dakota, connecting cities such as Kansas City, Sioux City, and Fargo.
  • E. Interstate 30
    Interstate 30 is a major east–west U.S. highway running through Texas and Arkansas, connecting cities such as Dallas and Fort Worth to Little Rock.
  • 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_69a4935783b8819082b77726ec10cc42 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49b9bf0cc8190a145ccd6fc501349 completed March 1, 2026, 8:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae0a8b7ad481909f6b44dad1d8b2ac completed March 8, 2026, 11:47 p.m.
Created at: March 1, 2026, 7:33 p.m.