Triple
T2804313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dersingham Bog |
E54015
|
entity |
| Predicate | near |
P350
|
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, near, Dersingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dersingham Context triple: [Dersingham Bog, near, 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.
Etchingham
Etchingham is a rural village and civil parish in East Sussex, England, known for its historic church and location in the Rother district.
-
C.
Wimbotsham
Wimbotsham is a small village and civil parish in Norfolk, England, known for its rural character and historic church.
-
D.
Stalham
Stalham is a small market town in Norfolk, England, known as a gateway to the Norfolk Broads.
-
E.
Cudham
Cudham is a historic rural village in southeast England, known for its traditional character and countryside setting within Greater London.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde1409148190a06a401185a26b64 |
completed | March 7, 2026, 8:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc674217c81908177b088cc824e7b |
completed | March 10, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:59 p.m.