Triple
T5483732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Lindsey |
E123526
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Bardney |
E158272
|
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: Bardney | Statement: [West Lindsey, hasSettlement, Bardney]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bardney Context triple: [West Lindsey, hasSettlement, Bardney]
-
A.
Bardney
chosen
Bardney is a village and civil parish in Lincolnshire, England, known historically for its medieval abbey and its location near the River Witham.
-
B.
Buntingford
Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
-
C.
Bardwell
Bardwell is a small rural village and civil parish in the county of Suffolk in eastern England.
-
D.
Brough
Brough is a village and civil parish in the East Riding of Yorkshire, England, situated on the northern bank of the Humber Estuary.
-
E.
Kintbury
Kintbury is a rural village in Berkshire, England, known for its picturesque countryside setting and historic charm.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd925deadc81908e193eeb75b63d90 |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48a4c67081909fb62ddcf0fb3047 |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:10 p.m.