Triple
T19556543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thorne |
E489326
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Thorne 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: Thorne Lock | Statement: [Thorne, hasLandmark, Thorne Lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thorne Lock Context triple: [Thorne, hasLandmark, Thorne Lock]
-
A.
Thorne Lock
chosen
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.
-
B.
Thurmaston Lock
Thurmaston Lock is a navigation lock on the River Soar in Leicestershire, England, used to manage water levels and enable boat passage along the river.
-
C.
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.
-
D.
Sandford Lock
Sandford Lock is a navigation lock on the River Chelmer in Essex, England, used to manage water levels and enable boat passage along the river.
-
E.
Saltersford Lock
Saltersford Lock is a navigation lock on the River Weaver in Cheshire, 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 (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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d341d708190b8ef35822f8bfe7c |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 10, 2026, 1:42 p.m.