Triple

T6006958
Position Surface form Disambiguated ID Type / Status
Subject M57 E133734 entity
Predicate routeNumber P1864 FINISHED
Object M57 E363159 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: M57 | Statement: [M57, routeNumber, M57]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M57
Context triple: [M57, routeNumber, M57]
  • A. M57 chosen
    M57 is a major motorway in Merseyside, England, forming part of the road network serving the Sefton area and connecting it to other key routes in the region.
  • B. M56
    The M56 is a major motorway in North West England that connects Manchester to North Wales and serves as a key route to Manchester Airport.
  • C. M59
    M59 is an elliptical galaxy located in the constellation Virgo and is one of the prominent members of the Virgo Cluster.
  • D. M-5
    M-5 is a state highway in southeastern Michigan that serves as a key commuter route connecting Novi and surrounding suburbs to the Detroit metropolitan area.
  • E. M67
    M67 is a short motorway in Greater Manchester, England, connecting the M60 near Denton towards Hyde and intended as the first section of an unrealized trans-Pennine route.
  • 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_69c00872444c8190bfaf1739dcec765c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f13d9908190a11d9bef8652db93 completed March 22, 2026, 8:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c10895559081908b9efdd32ecef37f completed March 23, 2026, 9:32 a.m.
Created at: March 22, 2026, 4:06 p.m.