Triple

T21390091
Position Surface form Disambiguated ID Type / Status
Subject Utica, Michigan E527619 entity
Predicate roadAccess P385 FINISHED
Object M-59 NE NERFINISHED

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: M-59 | Statement: [Utica, Michigan, roadAccess, M-59]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-59
Context triple: [Utica, Michigan, roadAccess, M-59]
  • A. M-59 chosen
    M-59 is an east–west state highway in southeastern Michigan that serves as a major suburban arterial route connecting communities north of Detroit.
  • B. M-55
    M-55 is a state trunkline highway in Michigan that runs east–west across the northern Lower Peninsula, connecting several communities including the city of Manistee.
  • C. M-52
    M-52 is a state highway in Michigan that runs north–south through several counties, serving as an important regional route for local and through traffic.
  • D. M-50
    M-50 is a state trunkline highway in Michigan that runs east–west across the southern part of the state, connecting several communities and major routes.
  • E. M-50
    M-50 is a major orbital motorway around Madrid, Spain, designed to divert traffic from the city center and connect key suburbs and highways.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0f8ae288190b43df9fe2841a822 completed April 22, 2026, 11:28 a.m.
Created at: April 16, 2026, 5:13 p.m.