Triple
T21187527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torksey |
E522120
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Saxilby |
—
|
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: Saxilby | Statement: [Torksey, nearbySettlement, Saxilby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saxilby Context triple: [Torksey, 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.
Scamblesby
Scamblesby is a small rural village in Lincolnshire, England, situated in the scenic Lincolnshire Wolds.
-
C.
Sileby
Sileby is a large village and civil parish in Leicestershire, England, known historically for its hosiery and shoe industries and its location between Loughborough and Leicester.
-
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.
Aylesby
Aylesby is a small rural village and civil parish in North East Lincolnshire, England, known for its historic church and agricultural surroundings.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7302222788190aa55ee0ed7342498 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 3:07 p.m.