Triple

T30489001
Position Surface form Disambiguated ID Type / Status
Subject Trent Lock junction E775805 entity
Predicate accessFromWaterway P31589 FINISHED
Object Erewash Canal 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: Erewash Canal | Statement: [Trent Lock junction, accessFromWaterway, Erewash Canal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessFromWaterway
Context triple: [Trent Lock junction, accessFromWaterway, Erewash Canal]
  • A. waterwayAccess chosen
    Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
  • B. hasWaterfrontAccessTo
    Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
  • C. associatedWithWaterways
    Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
  • D. usedWaterway
    Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
  • 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_69f22497f91c8190afa7165bc900accd completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f707f7959881908f037f0d6b1d0c36 completed May 3, 2026, 8:31 a.m.
PD Predicate disambiguation batch_69f700fc274c8190a128593dc7c7abd0 completed May 3, 2026, 8:02 a.m.
Created at: April 29, 2026, 8:13 p.m.