Triple
T10976136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bow Locks |
E259373
|
entity |
| Predicate | connectsNavigationBetween |
P12116
|
FINISHED |
| Object | Lee Navigation and tidal Thames via Bow Creek |
—
|
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: Lee Navigation and tidal Thames via Bow Creek | Statement: [Bow Locks, connectsNavigationBetween, Lee Navigation and tidal Thames via Bow Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsNavigationBetween Context triple: [Bow Locks, connectsNavigationBetween, Lee Navigation and tidal Thames via Bow Creek]
-
A.
enablesNavigationBetween
chosen
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
B.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
C.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
D.
navigationLinkedTo
Indicates that one element is connected to another as a navigational target or destination, enabling movement or access between them.
-
E.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f5bef481909043656c571fda89 |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.