Triple

T1282354
Position Surface form Disambiguated ID Type / Status
Subject Chertsey E27353 entity
Predicate servedByRoad P385 FINISHED
Object A320 road E151908 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: A320 road | Statement: [Chertsey, servedByRoad, A320 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A320 road
Context triple: [Chertsey, servedByRoad, A320 road]
  • A. A320 road chosen
    The A320 road is a primary route in Surrey, England, connecting the town of Guildford with Woking and Chertsey and linking local traffic to major motorways.
  • B. A322 road
    The A322 road is a primary route in southern England connecting the M3 near Lightwater with the M4 near Bracknell, serving towns such as Bagshot along its course.
  • C. A3211 road
    The A3211 road is a major route running through central London along the north bank of the River Thames, connecting key areas such as the City of London and Westminster.
  • D. A3 road
    The A3 road is a major trunk route in England that connects London to Portsmouth, passing through counties such as Surrey.
  • E. A30 road
    The A30 road is a major trunk route in southern England that runs from London through counties including Surrey toward the southwest.
  • 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_69a496d3710c8190955dee8bc0dacb50 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c0b47be08190828a1c0a11d94ce8 completed March 1, 2026, 10:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69acc6209a388190b9f018b63120b28c completed March 8, 2026, 12:43 a.m.
Created at: March 1, 2026, 7:50 p.m.