Triple
T12918138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxmundham |
E309042
|
entity |
| Predicate | hasNeighbouringSettlement |
P4647
|
FINISHED |
| Object | Leiston |
E299690
|
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: Leiston | Statement: [Saxmundham, hasNeighbouringSettlement, Leiston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leiston Context triple: [Saxmundham, hasNeighbouringSettlement, Leiston]
-
A.
Leiston
chosen
Leiston is a small town in eastern England known for its industrial heritage and proximity to the Suffolk coast.
-
B.
Denston
Denston is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
C.
Willoughby
Willoughby is a tranquil, nostalgic small town that serves as the idyllic setting in the classic The Twilight Zone episode "A Stop at Willoughby."
-
D.
Willoughby
Willoughby is a rapidly growing residential and commercial neighbourhood in the Township of Langley in British Columbia, Canada.
-
E.
Bildeston
Bildeston is a historic village and civil parish located in the county of Suffolk in eastern England.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e6d9fc8190b8a5244b26b5f78a |
completed | April 10, 2026, 9:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a572b0548190bd91e29998409fde |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:41 p.m.