Triple
T16580779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A614 |
E402823
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Bawtry |
E269076
|
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: Bawtry | Statement: [A614, passesNear, Bawtry]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bawtry Context triple: [A614, passesNear, Bawtry]
-
A.
Bawtry
chosen
Bawtry is a small historic market town in South Yorkshire, England, known for its traditional high street and role as a local commercial and transport hub.
-
B.
Kilworth
Kilworth is a small village in County Cork, Ireland, known for its rural setting and proximity to the Galtee Mountains.
-
C.
Scawby
Scawby is a rural village and civil parish in North Lincolnshire, England, known for its historic estate and traditional English countryside setting.
-
D.
Buxworth
Buxworth is a small village in the High Peak district of Derbyshire, England, known historically for its canal basin and industrial heritage.
-
E.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35960834c819080eed0c9f32b881d |
completed | April 18, 2026, 10:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ef0bc4c8190b06b03c06d344abf |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:16 a.m.