Triple
T17788681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellingham |
E444091
|
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: [Bellingham, near, Beckenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beckenham Context triple: [Bellingham, 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.
Beckenham
Beckenham is a residential suburb of Christchurch, New Zealand, known for its leafy streets, riverside reserves, and family-friendly character.
-
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.
Beddington
Beddington is a suburban area in South London known for its historic village core, green spaces, and proximity to Croydon and central London.
-
E.
Merstham
Merstham is a village and suburb in Surrey, England, known for its historic centre and proximity to the town of Redhill.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879524bc819090855ab5248c73db |
completed | April 19, 2026, 7:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07ea25b7fc819093c2eb248e705c6b |
completed | May 16, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:12 a.m.