Triple
T10069746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chessington |
E213588
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Tolworth |
E582175
|
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: Tolworth | Statement: [Chessington, locatedNear, Tolworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tolworth Context triple: [Chessington, locatedNear, Tolworth]
-
A.
Tolworth
chosen
Tolworth is a suburban area in the Royal Borough of Kingston upon Thames in southwest London, England.
-
B.
Tadworth
Tadworth is a suburban village in Surrey, England, situated on the North Downs and known for its residential character and proximity to Epsom Downs.
-
C.
Weybridge
Weybridge is a suburban town in southeast England known for its affluent residential areas and proximity to the River Thames and major transport links into London.
-
D.
Merstham
Merstham is a village and suburb in Surrey, England, known for its historic centre and proximity to the town of Redhill.
-
E.
Witley
Witley is a village and civil parish in Surrey, England, known for its rural character and historic buildings within the Borough of Waverley.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcffa045c8190a08db0bb74cb006a |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d32a950bc081909699d6bb31935cbd |
completed | April 6, 2026, 3:37 a.m. |
Created at: March 30, 2026, 8:58 p.m.