Triple
T12623158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levington |
E301439
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bucklesham |
E299716
|
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: Bucklesham | Statement: [Levington, locatedNear, Bucklesham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bucklesham Context triple: [Levington, locatedNear, Bucklesham]
-
A.
Bucklesham
chosen
Bucklesham is a small village and civil parish in Suffolk, England, situated near the county’s eastern coast.
-
B.
Shottisham
Shottisham is a small rural village and civil parish in the English county of Suffolk, known for its traditional countryside character and historic church.
-
C.
Betsham
Betsham is a small village in Kent, England, situated within the DA (Dartford) postcode area.
-
D.
Bickenhill
Bickenhill is a village in the West Midlands of England, notable for its proximity to major transport hubs and urban centers including Birmingham.
-
E.
Blunham
Blunham is a village in Bedfordshire, England, known for its rural setting near the River Ivel and historic parish church.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d960c8671881909a102d28b0e7f603 |
completed | April 10, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ed6f79881908872c644a9789f04 |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:14 p.m.