Triple
T12624040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dersingham Bog |
E301463
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Dersingham |
E54015
|
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: Dersingham | Statement: [Dersingham Bog, locatedNear, Dersingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dersingham Context triple: [Dersingham Bog, locatedNear, Dersingham]
-
A.
Dersingham
chosen
Dersingham is a coastal village in Norfolk, England, known for its proximity to the Royal Sandringham Estate and the nearby Dersingham Bog nature reserve.
-
B.
Hensingham
Hensingham is a residential suburb of Whitehaven in Cumbria, England, known for its local community facilities and proximity to the town’s centre.
-
C.
Bassingham
Bassingham is a small rural village and civil parish in the North Kesteven district of Lincolnshire, England.
-
D.
Itteringham
Itteringham is a small rural village in Norfolk, England, known for its historic buildings and picturesque countryside setting.
-
E.
Gressingham
Gressingham is a small rural village in Lancashire, England, known for its picturesque setting near the River Lune.
- 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_69d9610a897c8190a96f3c78d4b270a2 |
completed | April 10, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6686d770881909850ffaf820171d9 |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:14 p.m.