Triple
T21269406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham–Skegness line |
E524215
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Bottesford |
—
|
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: Bottesford | Statement: [Nottingham–Skegness line, passesThrough, Bottesford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bottesford Context triple: [Nottingham–Skegness line, passesThrough, Bottesford]
-
A.
Bottesford
chosen
Bottesford is a village in Leicestershire, England, known for its historic parish church and rural setting near the River Devon.
-
B.
Burford
Burford is a historic medieval market town in Oxfordshire, England, often regarded as one of the most picturesque settlements in the Cotswolds.
-
C.
Battisford
Battisford is a small rural village and civil parish located in the English county of Suffolk.
-
D.
Batesford
Batesford is a small rural township in Victoria, Australia, located just west of Geelong and known for its historic bridge and surrounding farming landscape.
-
E.
Botesdale
Botesdale is a small rural village in Suffolk, England, known for its historic buildings and traditional village character.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:01 p.m.