Triple
T14736030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ancholme |
E346209
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Barnetby |
E428094
|
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: Barnetby | Statement: [River Ancholme, passesNear, Barnetby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barnetby Context triple: [River Ancholme, passesNear, Barnetby]
-
A.
Barnetby
chosen
Barnetby is a village and railway junction in North Lincolnshire, England, known for its busy rail connections on routes across northern and eastern England.
-
B.
Barnby
Barnby is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
C.
Barrowby
Barrowby is a village in Lincolnshire, England, known for its rural character and proximity to the market town of Grantham.
-
D.
Navenby
Navenby is a historic village and civil parish in Lincolnshire, England, known for its traditional architecture and rural character.
-
E.
Bredenbury
Bredenbury is a small rural village and civil parish in Herefordshire, England, known for its countryside setting near the market town of Bromyard.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73114cc819088e1101b689fc70b |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb8e0d488190851d73b75ba4c0a6 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.