Triple
T8733877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepperton Lock |
E207324
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Weybridge |
E25035
|
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: Weybridge | Statement: [Shepperton Lock, locatedNear, Weybridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weybridge Context triple: [Shepperton Lock, locatedNear, Weybridge]
-
A.
Weybridge
chosen
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.
-
B.
Surbiton
Surbiton is a suburban area in southwest London, England, known for its commuter links to central London and its leafy residential character.
-
C.
Teddington
Teddington is a suburban town in southwest London, England, known for its riverside location on the Thames and proximity to several royal parks.
-
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.
Purley
Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d2a26988190acfda17f232e610a |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d32a1e1de88190a98ce4b6aea1a148 |
completed | April 6, 2026, 3:35 a.m. |
Created at: March 30, 2026, 6:37 p.m.