Triple

T14631984
Position Surface form Disambiguated ID Type / Status
Subject Dorchester E343498 entity
Predicate roadServedBy P385 FINISHED
Object A37 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: A37 road | Statement: [Dorchester, roadServedBy, A37 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A37 road
Context triple: [Dorchester, roadServedBy, A37 road]
  • A. A37 road chosen
    The A37 road is a major route in southwest England that runs between Bristol and Dorchester, passing through rural areas and towns in Somerset and Dorset.
  • B. A374 road
    The A374 road is a primary route in southwest England that links Plymouth in Devon with Torpoint and other parts of southeast Cornwall.
  • C. A307 road
    The A307 road is a key route in southeast England that runs through parts of Surrey and southwest London, connecting towns such as Esher with the London area.
  • D. A337 road
    The A337 road is a primary route in southern England that runs through the New Forest area, connecting towns such as Lymington and Lyndhurst.
  • E. 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.
  • 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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4a912248190a3df7f821395c776 completed April 14, 2026, 9:42 p.m.
Created at: April 10, 2026, 1:26 a.m.