Triple
T13759726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kempston |
E330570
|
entity |
| Predicate | hasNeighbouringSettlement |
P4647
|
FINISHED |
| Object | Bromham |
E593530
|
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: Bromham | Statement: [Kempston, hasNeighbouringSettlement, Bromham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bromham Context triple: [Kempston, hasNeighbouringSettlement, Bromham]
-
A.
Bromham
chosen
Bromham is a village in Wiltshire, England, known in part as the place where the Irish poet and songwriter Thomas Moore died.
-
B.
Bromyard
Bromyard is a small market town in Herefordshire, England, known for its rural setting and traditional local festivals.
-
C.
Brantham
Brantham is a village and civil parish in Suffolk, England, situated near the River Stour close to the Essex border.
-
D.
Bradenham
Bradenham is a village in Norfolk, England, known for its rural setting and proximity to the River Wissey.
-
E.
Burghfield
Burghfield is a village and civil parish in Berkshire, England, known for its rural character and proximity to Reading.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0223ab9081909db05334860405e0 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b06faed88190abc44e6256cb9301 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 10:09 p.m.