Triple

T10129968
Position Surface form Disambiguated ID Type / Status
Subject Foss Dyke E226310 entity
Predicate nearbySettlement P350 FINISHED
Object Saxilby E522117 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: Saxilby | Statement: [Foss Dyke, nearbySettlement, Saxilby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saxilby
Context triple: [Foss Dyke, nearbySettlement, Saxilby]
  • A. Saxilby chosen
    Saxilby is a village and civil parish in Lincolnshire, England, situated near the city of Lincoln along the Fossdyke Navigation.
  • B. Spilsby
    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.
  • 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. Navenby
    Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
  • 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_69ca843057b48190a86730167f5d6b98 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cdd33438988190be45878f98695816 completed April 2, 2026, 2:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2cc7c50b08190a04aa2f58a6c300a completed April 5, 2026, 8:56 p.m.
Created at: March 30, 2026, 9:05 p.m.