Triple

T7201119
Position Surface form Disambiguated ID Type / Status
Subject M-3 highway E168745 entity
Predicate hasJunctionWith P1018 FINISHED
Object M-2 highway E167507 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-2 highway | Statement: [M-3 highway, hasJunctionWith, M-2 highway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-2 highway
Context triple: [M-3 highway, hasJunctionWith, M-2 highway]
  • A. M-2 highway chosen
    The M-2 highway is a major Russian federal road that connects Moscow with the southern regions toward the border with Ukraine, serving as an important transport corridor through Moscow Oblast.
  • B. M-28 highway
    M-28 highway is a major east–west state trunkline in Michigan’s Upper Peninsula that serves as a key transportation route across the region.
  • C. M-1 highway
    The M-1 highway is a major Russian federal road that connects Moscow with the border of Belarus as part of the international route between Moscow and Western Europe.
  • D. M-3 highway
    The M-3 highway is a major Russian federal road that connects Moscow with the southwestern regions of the country and onward toward the border with Ukraine.
  • E. M-59 freeway
    The M-59 freeway is a major east–west highway in southeastern Michigan that serves as a key commuter and commercial route through suburbs north of Detroit.
  • 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_69c68a5376748190bb500f03df86e93e completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6e94971508190bb38184c9af2fe51 completed March 27, 2026, 8:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bfb0f4688190a677b818a0b3619c completed March 28, 2026, 11:46 a.m.
Created at: March 27, 2026, 2:52 p.m.