Triple

T5902287
Position Surface form Disambiguated ID Type / Status
Subject Kesteven E131255 entity
Predicate containsSettlement P847 FINISHED
Object Ancaster E174603 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: Ancaster | Statement: [Kesteven, containsSettlement, Ancaster]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ancaster
Context triple: [Kesteven, containsSettlement, Ancaster]
  • A. Ancaster chosen
    Ancaster is a village and civil parish in the South Kesteven district of Lincolnshire, England, known for its Roman history and archaeological remains.
  • B. Morpeth
    Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
  • C. Uttoxeter
    Uttoxeter is a historic market town in central England known for its racecourse and rural Staffordshire setting.
  • D. Southwell
    Southwell is a small coastal settlement on the Isle of Portland in Dorset, England, known for its proximity to dramatic cliffs and quarrying heritage.
  • E. Retford
    Retford is a historic market town in the English county of Nottinghamshire, known for its traditional town center and transport links.
  • 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_69c0085864a88190a569c05ff7d65f29 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03735e6f8819084eded3b45f5e4ed completed March 22, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b16297588190928693a7c31ec0a7 completed March 23, 2026, 3:20 a.m.
Created at: March 22, 2026, 3:58 p.m.