Triple

T23779168
Position Surface form Disambiguated ID Type / Status
Subject Coventry Canal at Hawkesbury Junction E587761 entity
Predicate meetsWaterway P153905 FINISHED
Object Coventry 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: Coventry Canal | Statement: [Coventry Canal at Hawkesbury Junction, meetsWaterway, Coventry Canal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: meetsWaterway
Context triple: [Coventry Canal at Hawkesbury Junction, meetsWaterway, Coventry Canal]
  • A. 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.
  • B. mouthOfWatercourse
    Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
  • C. mouthOfTheWatercourse
    Indicates the location where a watercourse ends and flows into a larger body of water.
  • D. hasBodyOfWaterDrainedBy
    Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
  • E. waterwayServed
    Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
  • F. None of above. chosen

Provenance (4 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_69e2490d245881909028226a1393d624 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1c62ad61c8190a552e88bce2bad1c completed April 29, 2026, 8:49 a.m.
PD Predicate disambiguation batch_69f155f79e34819080f9ddb972b34deb completed April 29, 2026, 12:51 a.m.
PDg Predicate description generation batch_69f15ed138f88190a8ae555422978908 completed April 29, 2026, 1:28 a.m.
Created at: April 17, 2026, 7:16 p.m.