Triple
T3089550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffolk |
E64456
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Beccles |
E299689
|
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: Beccles | Statement: [Suffolk, containsSettlement, Beccles]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beccles Context triple: [Suffolk, containsSettlement, Beccles]
-
A.
Beccles
chosen
Beccles is a historic market town and civil parish situated on the River Waveney in the county of Suffolk, England.
-
B.
Cleethorpes
Cleethorpes is a seaside resort town on the east coast of England, known for its sandy beaches, promenade, and traditional British holiday attractions.
-
C.
Bungay
Bungay is a historic market town and civil parish situated on the River Waveney in Suffolk, England.
-
D.
Aylsham
Aylsham is a historic market town in eastern England known for its traditional architecture and proximity to the Norfolk Broads.
-
E.
Mundesley
Mundesley is a coastal village and seaside resort on the North Sea in Norfolk, England, known for its sandy beaches and traditional holiday atmosphere.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20d8f788190b05b8b6b5042bc1a |
completed | March 8, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235a3ebac8190af9a25eeee778675 |
completed | March 12, 2026, 3:40 a.m. |
Created at: March 8, 2026, 3:03 p.m.