Triple
T8596164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chertsey Bridge |
E203550
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Shepperton Lock |
E207324
|
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: Shepperton Lock | Statement: [Chertsey Bridge, near, Shepperton Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shepperton Lock Context triple: [Chertsey Bridge, near, Shepperton Lock]
-
A.
Shepperton Lock
chosen
Shepperton Lock is a lock on the River Thames in England, used to manage river navigation and water levels near the town of Shepperton.
-
B.
Chertsey Lock
Chertsey Lock is a lock on the River Thames in Surrey, England, used to manage river navigation and water levels near the town of Chertsey.
-
C.
Hertford Lock
Hertford Lock is a navigation lock on the River Lea in Hertfordshire, England, used to manage water levels and enable boat passage along the waterway.
-
D.
Allington Lock
Allington Lock is a key navigation and flood-control lock on the River Medway in Kent, England, marking the tidal limit of the river.
-
E.
Thorne Lock
Thorne Lock is a canal lock on the Sheffield and South Yorkshire Navigation in South Yorkshire, England, used to raise and lower boats between different water levels.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c945dc8190a313c61c0db46187 |
completed | March 31, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebba872b8819098ba7525944bcce1 |
completed | April 2, 2026, 6:55 p.m. |
Created at: March 30, 2026, 6:23 p.m.