Triple

T15752476
Position Surface form Disambiguated ID Type / Status
Subject Greater Manchester road network E381879 entity
Predicate hasPart P35 FINISHED
Object A34 road 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: A34 road | Statement: [Greater Manchester road network, hasPart, A34 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A34 road
Context triple: [Greater Manchester road network, hasPart, A34 road]
  • A. A34 road chosen
    The A34 road is a major trunk route in England running from Winchester in Hampshire to Salford near Manchester, serving as a key north–south link and bypassing cities such as Oxford and Newbury.
  • B. A34 road
    The A34 road is a regional route in Northern Ireland that connects towns such as Lisnaskea, serving as an important local transport link.
  • C. A30 road
    The A30 road is a major trunk route in southern England that runs from London through counties including Surrey toward the southwest.
  • D. A33 road
    The A33 road is a major route in southern England connecting Reading and Basingstoke to Winchester and the M3 motorway.
  • E. A342 road
    The A342 road is a primary route in southern England that runs through Wiltshire, connecting towns such as Devizes and Upavon with the wider regional road network.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e05030e31081908c307a8dc7067db4 completed April 16, 2026, 2:57 a.m.
Created at: April 10, 2026, 4:47 a.m.