Triple

T16734000
Position Surface form Disambiguated ID Type / Status
Subject A10 road E406669 entity
Predicate passesThrough P225 FINISHED
Object Buntingford E196449 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: Buntingford | Statement: [A10 road, passesThrough, Buntingford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buntingford
Context triple: [A10 road, passesThrough, Buntingford]
  • A. Buntingford chosen
    Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
  • B. Belchford
    Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
  • C. Buckland
    Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
  • D. Buckland
    Buckland is a settled region of the Shire in J.R.R. Tolkien’s Middle-earth, lying east of the Brandywine River and known as the homeland of the Brandybuck family.
  • E. Buckland
    Buckland is a small historic community located within the Bull Run Mountains region of northern Virginia.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e39c38c9cc8190a3220cc3684388dc completed April 18, 2026, 2:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a009d4c723c8190ad92628f4164d11c completed May 10, 2026, 2:59 p.m.
Created at: April 10, 2026, 5:20 a.m.