Triple
T31548425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Forest Canoe Trail |
E804928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-distance paddling route |
C29215
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: long-distance paddling route Context triple: [Northern Forest Canoe Trail, instanceOf, long-distance paddling route]
-
A.
long-distance cycle route
A long-distance cycle route is a designated, often waymarked cycling corridor that spans substantial distances, connecting regions or countries and providing cyclists with a continuous, safe, and scenic path for multi-day journeys.
-
B.
long-distance hiking trail
A long-distance hiking trail is an extended, often multi-day walking route designed for recreational trekking through diverse natural landscapes, typically marked and maintained for continuous foot travel.
-
C.
long-distance hiking trail segment
A long-distance hiking trail segment is a defined portion of an extended hiking route, characterized by continuous path alignment, consistent difficulty and terrain, and clear start and end points used for planning, navigation, and management.
-
D.
national water trail
chosen
A national water trail is a designated waterway route recognized for its recreational, scenic, and conservation value, providing public access and facilities for activities like paddling, boating, and wildlife viewing.
-
E.
river expedition
A river expedition is a planned journey along a river, typically involving navigation, exploration, and often scientific, recreational, or educational objectives.
- F. None of above.
Provenance (1 batch)
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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:09 p.m.