Triple

T22985550
Position Surface form Disambiguated ID Type / Status
Subject Louth and Horncastle E571596 entity
Predicate hasTown P847 FINISHED
Object Horncastle NE NERFINISHED

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: Horncastle | Statement: [Louth and Horncastle, hasTown, Horncastle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horncastle
Context triple: [Louth and Horncastle, hasTown, Horncastle]
  • A. Horncastle chosen
    Horncastle is a historic market town in Lincolnshire, England, known for its antique shops and its location near the Lincolnshire Wolds.
  • B. Snaith
    Snaith is a small historic market town and civil parish in the East Riding of Yorkshire, England.
  • C. Thirsk
    Thirsk is a historic market town in northern England, best known as the home of veterinarian-author James Herriot and as a gateway to the North York Moors.
  • D. Haltwhistle
    Haltwhistle is a small town in Northumberland, England, known as a gateway to Hadrian’s Wall and the surrounding Tyne Valley countryside.
  • E. Heighington
    Heighington is a village in Lincolnshire, England, known for its historic character and proximity to the city of Lincoln.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b3c50481908bb3741ec9f40862 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f182996ee08190ab74014ee7ecac2b completed April 29, 2026, 4:01 a.m.
Created at: April 17, 2026, 3:49 p.m.