Triple
T19556280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinsley Locks |
E489319
|
entity |
| Predicate | raisesWaterwayTo |
P135236
|
FINISHED |
| Object | Sheffield canal basin level |
—
|
LITERAL 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: Sheffield canal basin level | Statement: [Tinsley Locks, raisesWaterwayTo, Sheffield canal basin level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisesWaterwayTo Context triple: [Tinsley Locks, raisesWaterwayTo, Sheffield canal basin level]
-
A.
raisesWaterway
chosen
Indicates that one entity elevates or increases the level, height, or flow of a waterway relative to another entity or state.
-
B.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
C.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
- F. None of above.
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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d341d708190b8ef35822f8bfe7c |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.