Triple

T10159808
Position Surface form Disambiguated ID Type / Status
Subject M5 E233858 entity
Predicate hasJunctionWith P1018 FINISHED
Object A38 road E273195 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: A38 road | Statement: [M5, hasJunctionWith, A38 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A38 road
Context triple: [M5, hasJunctionWith, A38 road]
  • A. A38 road chosen
    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.
  • B. A386 road
    The A386 road is a primary route in Devon, England, running between Plymouth and Bideford and serving towns such as Tavistock along the way.
  • C. A338 road
    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.
  • D. A3088 road
    The A3088 road is a primary route in Somerset, England, linking the town of Yeovil to the A303 trunk road and providing an important connection toward London and the South East.
  • E. 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.
  • 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_69ca848e80748190b91d1e04d35512c7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec5831e481909b48fdfa8f1c670b completed April 2, 2026, 4:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5b196bc8190a643f2b534497476 completed May 3, 2026, 7:13 a.m.
Created at: March 30, 2026, 9:09 p.m.