Triple

T12881601
Position Surface form Disambiguated ID Type / Status
Subject Camelford E308107 entity
Predicate hasRoad P959 FINISHED
Object A39 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: A39 road | Statement: [Camelford, hasRoad, A39 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A39 road
Context triple: [Camelford, hasRoad, A39 road]
  • A. A39 road chosen
    The A39 road is a major route in southwest England running along much of the north coast of Cornwall and Devon, linking several coastal towns and connecting with key trunk roads.
  • B. A339 road
    The A339 road is a primary route in southern England that connects Newbury in Berkshire with Basingstoke in Hampshire.
  • C. 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.
  • D. A34 road
    The A34 road is a major trunk route in England running from Winchester in Hampshire to Salford near Manchester, serving as a key north–south link and bypassing cities such as Oxford and Newbury.
  • 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 (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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d970fd15888190baf90fc30f2a3e25 completed April 10, 2026, 9:51 p.m.
Created at: April 9, 2026, 5:39 p.m.