Triple
T24996155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Road Lock |
E625572
|
entity |
| Predicate | onWaterwaySection |
P58979
|
FINISHED |
| Object | Regent's Canal through central-north London |
—
|
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: Regent's Canal through central-north London | Statement: [City Road Lock, onWaterwaySection, Regent's Canal through central-north London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onWaterwaySection Context triple: [City Road Lock, onWaterwaySection, Regent's Canal through central-north London]
-
A.
isWaterway
Indicates that one entity is a water-based route or channel (such as a river, canal, or sea lane) used for travel or transport.
-
B.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
C.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
D.
isOnWatercourse
chosen
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
E.
hasWaterwayRole
Indicates that an entity participates in or is associated with a waterway in a specific functional capacity or role.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a4a2c048190bfb5afe6df7ca3f0 |
completed | May 1, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:04 a.m.