Triple

T3223103
Position Surface form Disambiguated ID Type / Status
Subject Sale E67553 entity
Predicate hasRoadConnection P385 FINISHED
Object A56 road E140011 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: A56 road | Statement: [Sale, hasRoadConnection, A56 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A56 road
Context triple: [Sale, hasRoadConnection, A56 road]
  • A. A56 road chosen
    The A56 road is a major route in North West England connecting Chester to the Manchester area and beyond, serving as an important link between urban centers and the motorway network.
  • B. A560 road
    The A560 road is a significant route in Greater Manchester, England, connecting various suburbs and facilitating regional traffic flow.
  • C. A565 road
    The A565 road is a major route in North West England that connects Liverpool with Southport and other nearby towns, serving as an important commuter and regional traffic corridor.
  • D. A57 road
    The A57 road is a major route in England running between Liverpool and Lincoln, passing through cities such as Manchester and Sheffield.
  • E. A55 road
    The A55 road is a major dual carriageway in North Wales that forms part of the key east–west route along the North Wales coast, linking Chester to Holyhead and facilitating access to the port and the A5.
  • 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_69ad858b8adc8190ad989712c87a476b completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adae196da8819086fdcf5d2b21a702 completed March 8, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cfaae99194819095cf9b74267956a4 completed April 3, 2026, 11:56 a.m.
Created at: March 8, 2026, 3:08 p.m.