Triple
T21437460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Bedford |
E528849
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Biddenham |
—
|
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: Biddenham | Statement: [Borough of Bedford, hasSettlement, Biddenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Biddenham Context triple: [Borough of Bedford, hasSettlement, Biddenham]
-
A.
Biddenham
chosen
Biddenham is a village and civil parish in Bedfordshire, England, situated just west of the town of Bedford.
-
B.
Bradenham
Bradenham is a village in Norfolk, England, known for its rural setting and proximity to the River Wissey.
-
C.
Haddenham
Haddenham is a village and civil parish in Cambridgeshire, England, known for its rural character and historic parish church.
-
D.
Haddenham
Haddenham is a large village in Buckinghamshire, England, known for its historic architecture and rural setting near the town of Thame.
-
E.
Teversham
Teversham is a small village and civil parish located near Cambridge in the South Cambridgeshire district of England.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8140a1fc8190bedf297cfc4d4841 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 16, 2026, 6:03 p.m.