Triple
T3107326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Wickham |
E64862
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Beckenham |
E64122
|
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: Beckenham | Statement: [West Wickham, near, Beckenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beckenham Context triple: [West Wickham, near, Beckenham]
-
A.
Beckenham
chosen
Beckenham is a suburban town in southeast London known for its residential character, green spaces, and commuter links into central London.
-
B.
Westerham
Westerham is a small historic town in Kent, England, known for its picturesque setting and associations with figures such as Winston Churchill.
-
C.
Merstham
Merstham is a village and suburb in Surrey, England, known for its historic centre and proximity to the town of Redhill.
-
D.
Banstead
Banstead is a suburban town in southeast England known for its village-like high street and green spaces within the county of Surrey.
-
E.
Burgess Hill
Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed8f0f4088190ba66d5e3c6642c9a |
completed | March 21, 2026, 5:44 p.m. |
Created at: March 8, 2026, 3:04 p.m.