Triple
T757903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Trails System units |
E15998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federally designated long-distance trails system |
C2163
|
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: federally designated long-distance trails system Context triple: [National Trails System units, instanceOf, federally designated long-distance trails system]
-
A.
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.
-
B.
National Scenic Trail
chosen
A National Scenic Trail is a federally designated long-distance trail that offers outstanding recreational opportunities and showcases significant natural, scenic, and cultural landscapes across large geographic areas.
-
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.
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.
trail designation
A trail designation is a label or classification assigned to a trail that defines its permitted uses, difficulty level, regulatory status, and other management or user information.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.