Triple

T2966735
Position Surface form Disambiguated ID Type / Status
Subject Junction 9 of M60 motorway E80183 entity
Predicate onRoute P5619 FINISHED
Object M60 E76610 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: M60 | Statement: [Junction 9 of M60 motorway, onRoute, M60]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M60
Context triple: [Junction 9 of M60 motorway, onRoute, M60]
  • A. M60 chosen
    M60 is a major orbital motorway encircling the city of Manchester in Greater Manchester, England.
  • B. M60 SBS
    The M60 SBS is a Select Bus Service route in New York City that provides limited-stop service between Manhattan and Queens, including direct access to LaGuardia Airport.
  • C. M62
    M62 is a major trans-Pennine motorway in northern England connecting cities such as Liverpool, Manchester, Leeds, and Hull.
  • D. M60 machine gun
    The M60 machine gun is a 7.62×51mm NATO general-purpose machine gun developed by the United States and widely used by its military forces from the late 1950s onward.
  • E. M16
    M16 is the Osaka Metro station code assigned to Umeda Station on the Midosuji Line in Osaka, Japan.
  • 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_69ad8b1341848190bd19dbf46892887d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad996e93788190ba9883714d4dfa0c completed March 8, 2026, 3:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1eede693c8190a49be9d267bed6fa completed March 11, 2026, 10:38 p.m.
Created at: March 8, 2026, 2:58 p.m.