Triple

T7683909
Position Surface form Disambiguated ID Type / Status
Subject Swift Rapids Lock E174063 entity
Predicate hasProvinceParkSystem P78909 FINISHED
Object federal canal system of Canada 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: federal canal system of Canada | Statement: [Swift Rapids Lock, hasProvinceParkSystem, federal canal system of Canada]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProvinceParkSystem
Context triple: [Swift Rapids Lock, hasProvinceParkSystem, federal canal system of Canada]
  • A. hasRegionalPark
    Indicates that a place or administrative area contains or is served by a designated regional park.
  • B. stateParkSystem
    Indicates that an entity is part of, managed by, or associated with a state-level park system or network of state parks.
  • C. hasCountryPark
    Indicates that a place or administrative area contains or is associated with a designated country park.
  • D. hasNationalParkSite
    Indicates that a location, region, or jurisdiction contains or is home to at least one designated national park site.
  • E. hasNationalParkServicePresence
    Indicates that the National Park Service operates, manages, or maintains an official presence at the referenced location or entity.
  • 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_69c6995840408190a19de6c51090f46f completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7048b0b448190889bd40e0a38e51a completed March 27, 2026, 10:28 p.m.
PD Predicate disambiguation batch_69c701618d3481908be84b76f36ac5a1 completed March 27, 2026, 10:14 p.m.
PDg Predicate description generation batch_69c7048a01508190bc2e9ae8b863486c completed March 27, 2026, 10:28 p.m.
Created at: March 27, 2026, 4:01 p.m.