Triple
T4224234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lee |
E94414
|
entity |
| Predicate | hasFeature |
P182
|
FINISHED |
| Object | Tottenham Lock |
E259376
|
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: Tottenham Lock | Statement: [River Lee, hasFeature, Tottenham Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tottenham Lock Context triple: [River Lee, hasFeature, Tottenham Lock]
-
A.
Tottenham Lock
chosen
Tottenham Lock is a canal lock on the River Lea in North London, used to manage water levels and enable boat navigation along the river.
-
B.
Brentford Lock
Brentford Lock is a historic canal lock and waterside area on the Grand Union Canal in Brentford, west London, known for its maritime heritage and regenerated residential and leisure developments.
-
C.
Hatton Locks
Hatton Locks is a famous flight of canal locks near Warwick in England, known for its steep rise and historic role in enabling boat traffic along the Grand Union Canal.
-
D.
Shepperton Lock
Shepperton Lock is a lock on the River Thames in England, used to manage river navigation and water levels near the town of Shepperton.
-
E.
Bardney Lock
Bardney Lock is a navigation lock on the River Witham in Lincolnshire, England, used to manage water levels and enable boat passage along the river.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5964532e08190bb1dc56f734e6ebb |
completed | March 14, 2026, 5:09 p.m. |
Created at: March 12, 2026, 11:04 p.m.