Triple

T12756332
Position Surface form Disambiguated ID Type / Status
Subject Ann Arbor metropolitan area E304868 entity
Predicate hasStateHighway P385 FINISHED
Object M-14 E267563 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: M-14 | Statement: [Ann Arbor metropolitan area, hasStateHighway, M-14]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-14
Context triple: [Ann Arbor metropolitan area, hasStateHighway, M-14]
  • A. M-14 chosen
    M-14 is a state highway in southeastern Michigan that serves as a major commuter route connecting Ann Arbor with the western suburbs of the Detroit metropolitan area.
  • B. M-13
    M-13 is a state highway in Michigan that runs through the Saginaw Bay region, connecting communities such as Essexville with the broader state road network.
  • C. M-45
    M-45 is a state highway in Michigan that runs east–west through the Grand Rapids area toward the Lake Michigan shoreline.
  • D. M-45
    M-45 is a major ring road in the Madrid metropolitan area that helps divert traffic around the city and connect several eastern suburbs.
  • E. M-40
    M-40 is a major ring road encircling Madrid, Spain, serving as a key arterial route that connects various suburbs and municipalities around the city.
  • 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d8b57b88190b29b8fdca415c81c completed April 10, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c9aa6308190bfcb1511a561c0f9 completed May 2, 2026, 10:37 p.m.
Created at: April 9, 2026, 5:27 p.m.