Triple

T13870610
Position Surface form Disambiguated ID Type / Status
Subject Bolingbroke Castle E333437 entity
Predicate nearbySettlement P350 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: [Bolingbroke Castle, nearbySettlement, Spilsby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spilsby
Context triple: [Bolingbroke Castle, nearbySettlement, 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. Aylesby
    Aylesby is a small rural village and civil parish in North East Lincolnshire, England, known for its historic church and agricultural surroundings.
  • E. Vickleby
    Vickleby is a small village on the island of Öland in southeastern Sweden, known for its traditional rural landscape and historic church.
  • 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_69d81c5ced9c8190b0e9bcc6effe5959 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de05c638248190bbe5d19f7b88d0f9 completed April 14, 2026, 9:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c105da548190b908a54fec029236 completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:14 p.m.