Triple
T22598619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfberg Arch |
E574751
|
entity |
| Predicate | hasHikingRouteType |
P17835
|
FINISHED |
| Object | out-and-back trail |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: out-and-back trail | Statement: [Wolfberg Arch, hasHikingRouteType, out-and-back trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHikingRouteType Context triple: [Wolfberg Arch, hasHikingRouteType, out-and-back trail]
-
A.
hasHikingAccess
Indicates that one location or entity provides access or a connection to hiking trails or hiking areas.
-
B.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
-
C.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
-
D.
isHikingDestination
Indicates that a location serves as a destination or endpoint for hiking activities or routes.
-
E.
hasRecreationalRoute
chosen
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
- F. None of above.
Provenance (3 batches)
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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626aa0808190a43e65f6aaabfeb4 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.