Triple

T1536106
Position Surface form Disambiguated ID Type / Status
Subject South Kesteven E32551 entity
Predicate hasParish P35 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: [South Kesteven, hasParish, Ancaster]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ancaster
Context triple: [South Kesteven, hasParish, 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_69a885ea86308190998f6bc14bb91f8e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90829e60081909d3f9f79585e080e completed March 5, 2026, 4:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad30942dc481908de85bd2ca30c0bd completed March 8, 2026, 8:17 a.m.
Created at: March 4, 2026, 7:26 p.m.