Triple

T10573288
Position Surface form Disambiguated ID Type / Status
Subject US 23 E249546 entity
Predicate overlapsWith P1867 FINISHED
Object US 1 E378377 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 1 | Statement: [US 23, overlapsWith, US 1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: US 1
Context triple: [US 23, overlapsWith, US 1]
  • A. US 1 chosen
    US 1 is a major north–south U.S. highway running along the East Coast, serving as a key route through numerous states and cities from Florida to Maine.
  • B. US 4
    US 4 is a U.S. highway in the northeastern United States that runs east–west through New York, Vermont, and New Hampshire, connecting several regional cities and interstate routes.
  • C. US 7
    US 7 is a north–south U.S. highway in New England that runs from Connecticut through Massachusetts to Vermont, serving as a major regional route.
  • D. US 1/9
    US 1/9 is a concurrent section of U.S. Routes 1 and 9 that runs through northern New Jersey, serving as a major urban arterial and connector to routes into New York City.
  • E. US 1A
    US 1A is a series of alternate U.S. Highway 1 routes in Maine that serve as business loops and local connectors through coastal towns and cities.
  • 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.