Triple
T12535677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudbury |
E299682
|
entity |
| Predicate | hasNeighbouringTown |
P3883
|
FINISHED |
| Object | Long Melford |
E299693
|
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: Long Melford | Statement: [Sudbury, hasNeighbouringTown, Long Melford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Long Melford Context triple: [Sudbury, hasNeighbouringTown, Long Melford]
-
A.
Long Melford
chosen
Long Melford is a historic village in Suffolk, England, noted for its exceptionally long main street, medieval wool trade heritage, and well-preserved timber-framed buildings.
-
B.
Glemsford
Glemsford is a village and civil parish in the county of Suffolk in eastern England, known for its historic buildings and rural character.
-
C.
Mendlesham
Mendlesham is a rural village and civil parish in Suffolk, England, known for its historic church and traditional village character.
-
D.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
-
E.
Waldringfield
Waldringfield is a small riverside village in eastern England known for its scenic setting on the River Deben and sailing activities.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546d3b2081908d3e0659f8f13678 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6557a95d48190ac588807544f060f |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 9:57 p.m.