Triple
T15411364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benacre |
E368599
|
entity |
| Predicate | adjacentParish |
P22613
|
FINISHED |
| Object | Kessingland |
E299696
|
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: Kessingland | Statement: [Benacre, adjacentParish, Kessingland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kessingland Context triple: [Benacre, adjacentParish, Kessingland]
-
A.
Kessingland
chosen
Kessingland is a coastal village and civil parish in Suffolk, England, known for its long shingle beach and seaside tourism.
-
B.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
-
C.
Birkholm
Birkholm is a small, sparsely populated Danish island known for its tranquil natural environment and traditional village atmosphere in the South Funen Archipelago.
-
D.
Keadby
Keadby is a village in North Lincolnshire, England, known for its location on the River Trent and its nearby power station and transport links.
-
E.
Hellingly
Hellingly is a village and civil parish in East Sussex, England, known for its rural character 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea600b48190a3dbca1a68a2a1cd |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a7356548190af5651ab0bc03ab9 |
completed | May 9, 2026, 11:28 a.m. |
Created at: April 10, 2026, 3:20 a.m.