Triple

T16786865
Position Surface form Disambiguated ID Type / Status
Subject Spilsby E408001 entity
Predicate hasPostTown P2711 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: [Spilsby, hasPostTown, SPILSBY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SPILSBY
Context triple: [Spilsby, hasPostTown, 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. Dalby
    Dalby is a rural town in Queensland, Australia, known as an agricultural and service hub on the Darling Downs.
  • C. Saxilby
    Saxilby is a village and civil parish in Lincolnshire, England, situated near the city of Lincoln along the Fossdyke Navigation.
  • D. Sprowston
    Sprowston is a suburban town and civil parish on the outskirts of Norwich in Norfolk, England.
  • E. Thoralby
    Thoralby is a small rural village in the Yorkshire Dales of North Yorkshire, England, known for its traditional stone buildings and scenic surroundings.
  • 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_69d8839270588190886720d9519bbf8f completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b21b6a408190b0766138cc9a9ee2 completed April 18, 2026, 4:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00ab07bdcc819086479178e5b8b679 completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:22 a.m.