Triple
T10521214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames Ditton |
E248173
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Long Ditton |
E424505
|
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: Long Ditton | Statement: [Thames Ditton, nearbySettlement, Long Ditton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Long Ditton Context triple: [Thames Ditton, nearbySettlement, Long Ditton]
-
A.
Long Ditton
chosen
Long Ditton is a suburban village in Surrey, England, forming part of the London commuter belt and known for its residential character and proximity to the River Thames.
-
B.
Thames Ditton
Thames Ditton is a suburban riverside village in Surrey, England, known for its picturesque setting on the River Thames and proximity to southwest London.
-
C.
Datchet
Datchet is a riverside village and civil parish in Berkshire, England, situated on the River Thames near Windsor.
-
D.
Bennetts End
Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
-
E.
Twyford
Twyford is a village and civil parish in Berkshire, England, known as a commuter settlement between Reading and 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d933f2d9e48190a4c5d5d5bdc0d7d8 |
completed | April 10, 2026, 5:31 p.m. |
Created at: April 6, 2026, 12:28 p.m.