Triple
T5853914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Bicycle Route 76 |
E130103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-distance cycling route |
C16763
|
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 cycling route Context triple: [U.S. Bicycle Route 76, instanceOf, long-distance cycling route]
-
A.
long-distance cycle route
chosen
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.
road cycling race
A road cycling race is a competitive event where cyclists ride on paved roads over a set course and distance, aiming to achieve the fastest time or best overall performance.
-
D.
long-distance footpath
A long-distance footpath is an extended, often waymarked walking route designed for multi-day journeys across varied landscapes, typically connecting towns, natural landmarks, or regions.
-
E.
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.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:55 p.m.