Triple
T36171815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Highlands Trail corridor |
E1046162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-distance hiking trail corridor |
C3572
|
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 hiking trail corridor Context triple: [New Jersey Highlands Trail corridor, instanceOf, long-distance hiking trail corridor]
-
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.
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.
-
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
chosen
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.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.