Triple

T16970592
Position Surface form Disambiguated ID Type / Status
Subject Harnham E411663 entity
Predicate crossedBy P416 FINISHED
Object A338 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: A338 road | Statement: [Harnham, crossedBy, A338 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A338 road
Context triple: [Harnham, crossedBy, A338 road]
  • A. A338 road chosen
    The A338 road is a major route in southern England that runs from Poole in Dorset to Besselsleigh near Oxford, connecting several towns and communities along its length.
  • B. A308 road
    The A308 road is a significant route in southern England that connects parts of London with towns in Surrey and Berkshire, running near the River Thames and serving both local and through traffic.
  • C. A38 road
    The A38 road is a major trunk route in England that runs from Bodmin in Cornwall to Mansfield in Nottinghamshire, connecting numerous cities and intersecting several key highways.
  • D. A348 road
    The A348 road is a primary route in Dorset, England, connecting the town of Ferndown with Bournemouth and other nearby settlements.
  • E. A33 road
    The A33 road is a major route in southern England connecting Reading and Basingstoke to Winchester and the M3 motorway.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0ac23a48190992fa125fceb1eb2 completed April 18, 2026, 6:42 p.m.
Created at: April 10, 2026, 5:31 a.m.