Triple

T14477378
Position Surface form Disambiguated ID Type / Status
Subject Spilsby, Lincolnshire, England E359007 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, Lincolnshire, England, hasPostTown, SPILSBY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SPILSBY
Context triple: [Spilsby, Lincolnshire, England, 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. Thoralby
    Thoralby is a small rural village in the Yorkshire Dales of North Yorkshire, England, known for its traditional stone buildings and scenic surroundings.
  • E. Nockeby
    Nockeby is a residential district in western Stockholm, Sweden, known as the terminus of one of the city's historic tram lines.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9248edb48190a74eb032aeaac027 completed April 14, 2026, 7:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd64a0553081909fd88d8f39ed1a01 completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:20 a.m.