Triple

T7705549
Position Surface form Disambiguated ID Type / Status
Subject Ancaster E174603 entity
Predicate locatedNear P294 FINISHED
Object Sleaford E77486 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: Sleaford | Statement: [Ancaster, locatedNear, Sleaford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sleaford
Context triple: [Ancaster, locatedNear, Sleaford]
  • A. Sleaford chosen
    Sleaford is a market town in Lincolnshire, England, known for its historic architecture and role as a local commercial and agricultural center.
  • B. Sleaford and North Hykeham
    Sleaford and North Hykeham is a UK parliamentary constituency in Lincolnshire, represented in the House of Commons.
  • C. Stallingborough
    Stallingborough is a village and civil parish in North East Lincolnshire, England, known for its rural character and proximity to the Humber Estuary.
  • D. Stowmarket
    Stowmarket is a market town in Suffolk, England, known for its historic town center and location on the River Gipping between Ipswich and Bury St Edmunds.
  • E. Towcester
    Towcester is a historic market town in Northamptonshire, England, known for its Roman origins and location on the ancient Watling Street route.
  • 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_69c6995b3e8c8190833108f883d5f53c completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7028f17f0819081686ac146750d3a completed March 27, 2026, 10:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8acc088148190ba5ba07e4ad2284c completed March 29, 2026, 4:38 a.m.
Created at: March 27, 2026, 4:03 p.m.