Triple

T17702552
Position Surface form Disambiguated ID Type / Status
Subject Verchères E441343 entity
Predicate locatedOnWaterwayUsedFor P5565 FINISHED
Object St. Lawrence Seaway navigation 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: St. Lawrence Seaway navigation | Statement: [Verchères, locatedOnWaterwayUsedFor, St. Lawrence Seaway navigation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedOnWaterwayUsedFor
Context triple: [Verchères, locatedOnWaterwayUsedFor, St. Lawrence Seaway navigation]
  • A. locatedOnWaterbody
    Indicates that an entity is situated on or directly adjacent to a specified body of water.
  • B. usedWaterway
    Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
  • C. associatedWithWaterways
    Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
  • D. waterwayServed chosen
    Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
  • E. 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.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4715c3980819094b080a871df1100 completed April 19, 2026, 6:08 a.m.
PD Predicate disambiguation batch_69e3cde601d4819097903f471f1fe99a completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 10:05 a.m.