Triple
T12179408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tendring District |
E290177
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Dovercourt |
E591225
|
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: Dovercourt | Statement: [Tendring District, containsSettlement, Dovercourt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dovercourt Context triple: [Tendring District, containsSettlement, Dovercourt]
-
A.
Dovercourt
chosen
Dovercourt is a coastal town in Essex, England, known for its sandy beaches and proximity to the port town of Harwich.
-
B.
Doveridge
Doveridge is a village in Derbyshire, England, known for its rural setting near the River Dove and its historic church and traditional English countryside character.
-
C.
Dallington
Dallington is a residential suburb of Christchurch, New Zealand, situated near the Avon River / Ōtākaro.
-
D.
Doyleston
Doyleston is a small rural settlement in the Canterbury region of New Zealand’s South Island.
-
E.
Fulbourn
Fulbourn is a village and civil parish located just southeast of Cambridge in the district of South Cambridgeshire, England.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fc451c819086a2a97967b82908 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6ab19288190a882c842d74a2e30 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:50 p.m.