Triple

T11823422
Position Surface form Disambiguated ID Type / Status
Subject Somersby, Lincolnshire, England E281194 entity
Predicate locatedNear P294 FINISHED
Object Spilsby E408001 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: Spilsby | Statement: [Somersby, Lincolnshire, England, locatedNear, Spilsby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spilsby
Context triple: [Somersby, Lincolnshire, England, locatedNear, Spilsby]
  • A. Spilsby chosen
    Spilsby is a small market town in Lincolnshire, England, known historically as the birthplace of explorer Sir John Franklin and for serving the surrounding rural agricultural area.
  • B. Saxilby
    Saxilby is a village and civil parish in Lincolnshire, England, situated near the city of Lincoln along the Fossdyke Navigation.
  • C. Barrowby
    Barrowby is a village in Lincolnshire, England, known for its rural character and proximity to the market town of Grantham.
  • D. Vickleby
    Vickleby is a small village on the island of Öland in southeastern Sweden, known for its traditional rural landscape and historic church.
  • E. Barnby
    Barnby is a small rural village and civil parish located in the county of Suffolk in eastern England.
  • 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_69d6ab276f8c8190b1966a0ef11349ac completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5e9c50481909b2287a0b23d2094 completed April 10, 2026, 7:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69f1671989f88190b8c1fb520435a25e completed April 29, 2026, 2:04 a.m.
Created at: April 8, 2026, 9:42 p.m.