Triple
T2709074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slaithwaite |
E59812
|
entity |
| Predicate | hasCanalFeature |
P26852
|
FINISHED |
| Object | lock flights on Huddersfield Narrow Canal |
—
|
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: lock flights on Huddersfield Narrow Canal | Statement: [Slaithwaite, hasCanalFeature, lock flights on Huddersfield Narrow Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanalFeature Context triple: [Slaithwaite, hasCanalFeature, lock flights on Huddersfield Narrow Canal]
-
A.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
B.
hasCanalSection
Indicates a relationship where one entity includes, contains, or is associated with a specific section or segment of a canal.
-
C.
hasCanalParallel
Indicates that one canal runs parallel to another canal without intersecting it.
-
D.
containsCanal
chosen
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
E.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda7542548190bbf6c947145f7f63 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.