Triple

T9147389
Position Surface form Disambiguated ID Type / Status
Subject north-west Kent E219491 entity
Predicate containsTown P847 FINISHED
Object Eynsford E267140 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: Eynsford | Statement: [north-west Kent, containsTown, Eynsford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eynsford
Context triple: [north-west Kent, containsTown, Eynsford]
  • A. Eynsford chosen
    Eynsford is a historic village in the Sevenoaks District of Kent, England, known for its medieval castle ruins and picturesque rural setting.
  • B. Aylesford
    Aylesford is a historic village in Kent, England, known for its ancient bridge, riverside setting, and archaeological significance.
  • C. Barrasford
    Barrasford is a small village in Northumberland, England, situated in the Tyne Valley and known for its rural setting and proximity to Hadrian’s Wall.
  • D. Farnworth
    Farnworth is a town in Greater Manchester, England, historically part of Lancashire and now largely residential with local industry and transport links to nearby urban centers.
  • E. Sharneyford
    Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
  • 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_69ca83e121dc81909912bd66953081c5 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca918a3c881909c34a6a682eb2625 completed April 1, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0482995cc81909bfc202cbab7f8a1 completed April 3, 2026, 11:07 p.m.
Created at: March 30, 2026, 7:20 p.m.