Triple
T22985557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louth and Horncastle |
E571596
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Spilsby |
—
|
NE NERFINISHED |
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: [Louth and Horncastle, hasTown, Spilsby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spilsby Context triple: [Louth and Horncastle, hasTown, 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.
Scamblesby
Scamblesby is a small rural village in Lincolnshire, England, situated in the scenic Lincolnshire Wolds.
-
C.
Swainby
Swainby is a small village in North Yorkshire, England, situated on the edge of the North York Moors and popular as a base for walking and outdoor activities.
-
D.
Brocklesby
Brocklesby is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural community and historic railway connections.
-
E.
Saxilby
Saxilby is a village and civil parish in Lincolnshire, England, situated near the city of Lincoln along the Fossdyke Navigation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182996ee08190ab74014ee7ecac2b |
completed | April 29, 2026, 4:01 a.m. |
Created at: April 17, 2026, 3:49 p.m.