Triple

T11284162
Position Surface form Disambiguated ID Type / Status
Subject Lullingstone Castle E267140 entity
Predicate locatedNear P294 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: [Lullingstone Castle, locatedNear, Eynsford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eynsford
Context triple: [Lullingstone Castle, locatedNear, 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9855e8881909bd301718cbd8ca1 completed April 9, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69e55639a5ec8190b979d5a280397f98 completed April 19, 2026, 10:24 p.m.
Created at: April 8, 2026, 9:31 p.m.