Triple
T25317220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batona Trail (segments) |
E634777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hiking trail segment collection |
C14948
|
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: hiking trail segment collection Context triple: [Batona Trail (segments), instanceOf, hiking trail segment collection]
-
A.
trail section collection
chosen
A trail section collection is an organized set of individual trail segments grouped together for management, analysis, or presentation as a unified route or network.
-
B.
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.
-
C.
long-distance hiking trail network
A long-distance hiking trail network is an interconnected system of marked footpaths spanning large geographic areas, designed to support extended, multi-day trekking experiences between various natural and cultural destinations.
-
D.
hiking trail access point
A hiking trail access point is a designated location where hikers can enter or exit a trail, often featuring signage, parking, and basic amenities.
-
E.
trail section
A trail section is a distinct, continuous segment of a larger trail network, defined by its start and end points, terrain characteristics, and associated difficulty or usage attributes.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:28 p.m.