Triple

T6062721
Position Surface form Disambiguated ID Type / Status
Subject Bardney Lock E135073 entity
Predicate locatedNear P294 FINISHED
Object Bardney E158272 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: Bardney | Statement: [Bardney Lock, locatedNear, Bardney]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bardney
Context triple: [Bardney Lock, locatedNear, Bardney]
  • A. Bardney chosen
    Bardney is a village and civil parish in Lincolnshire, England, known historically for its medieval abbey and its location near the River Witham.
  • B. Buntingford
    Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
  • C. Bardwell
    Bardwell is a small rural village and civil parish in the county of Suffolk in eastern England.
  • D. Biddenden
    Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
  • E. Brough
    Brough is a village and civil parish in the East Riding of Yorkshire, England, situated on the northern bank of the Humber Estuary.
  • 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_69c00878d06881909ee78e88913bf890 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0572100e8819084c3174921a2d527 completed March 22, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11d1e61188190aea0e2b1945ca682 completed March 23, 2026, 10:59 a.m.
Created at: March 22, 2026, 4:10 p.m.