Triple
T7162986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esher Common |
E166992
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Hersham |
E220696
|
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: Hersham | Statement: [Esher Common, near, Hersham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hersham Context triple: [Esher Common, near, Hersham]
-
A.
Hersham
chosen
Hersham is a suburban village in Surrey, England, situated near Walton-on-Thames and within commuting distance of London.
-
B.
Merstham
Merstham is a village and suburb in Surrey, England, known for its historic centre and proximity to the town of Redhill.
-
C.
Westerham
Westerham is a small historic town in Kent, England, known for its picturesque setting and associations with figures such as Winston Churchill.
-
D.
Harmondsworth
Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
-
E.
Chertsey
Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82feee481908fa180ea8c9924fa |
completed | March 27, 2026, 8:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbde8e8264819082a3954072dffd09 |
completed | March 31, 2026, 2:47 p.m. |
Created at: March 27, 2026, 2:47 p.m.