Triple

T10573197
Position Surface form Disambiguated ID Type / Status
Subject US 31 E249544 entity
Predicate connectsTo P845 FINISHED
Object US 231 E719028 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: US 231 | Statement: [US 31, connectsTo, US 231]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: US 231
Context triple: [US 31, connectsTo, US 231]
  • A. US 231 chosen
    US 231 is a major north–south United States highway running through several states in the eastern and central U.S., serving as an important regional transportation corridor.
  • B. US 23
    US 23 is a major north–south United States highway running from Florida to Michigan, serving as an important regional transportation corridor.
  • C. US 31
    US 31 is a major north–south United States highway running through several Midwestern and Southern states, serving as an important regional transportation corridor.
  • D. US 131
    US 131 is a north–south U.S. Highway in western Michigan that runs from the Indiana state line through cities such as Kalamazoo and Grand Rapids up toward the northern Lower Peninsula.
  • E. US 219
    US 219 is a north–south U.S. highway running through parts of New York, Pennsylvania, Maryland, and West Virginia, serving as a key regional route in the Appalachian region.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5274929cc81909a79d5e2049f7389 completed April 7, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d94b5d89748190bb398943e4a16e9b completed April 10, 2026, 7:11 p.m.
Created at: April 6, 2026, 12:37 p.m.