Triple
T21187530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torksey |
E522120
|
entity |
| Predicate | hasFeature |
P182
|
FINISHED |
| Object | Torksey Lock |
—
|
NE NERFINISHED |
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: Torksey Lock | Statement: [Torksey, hasFeature, Torksey Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Torksey Lock Context triple: [Torksey, hasFeature, Torksey Lock]
-
A.
Torksey Lock
chosen
Torksey Lock is a historic canal lock in Lincolnshire, England, where the Foss Dyke canal meets the River Trent, serving as an important junction for inland waterway navigation.
-
B.
Oxnead Lock
Oxnead Lock is a historic canal lock on the Aylsham Navigation in Norfolk, England, built to enable navigation along the River Bure.
-
C.
Kintbury Lock
Kintbury Lock is a historic lock on England’s Kennet and Avon Canal, serving boat traffic near the village of Kintbury in Berkshire.
-
D.
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.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7302222788190aa55ee0ed7342498 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 3:07 p.m.