Triple
T32447984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverview Park, Pittsburgh |
E829196
|
entity |
| Predicate | hasRecreationalTrailType |
P17835
|
FINISHED |
| Object | hiking trails |
—
|
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: hiking trails | Statement: [Riverview Park, Pittsburgh, hasRecreationalTrailType, hiking trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalTrailType Context triple: [Riverview Park, Pittsburgh, hasRecreationalTrailType, hiking trails]
-
A.
hasRecreationalRoute
chosen
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
B.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
-
C.
isHikingTrail
Indicates that a path or route is designated and used specifically for hiking activities.
-
D.
hasBikeTrailAccess
Indicates that an entity has direct access to, or is connected with, a bike trail suitable for cycling.
-
E.
hasTouristTrails
Indicates that an entity contains or is equipped with designated paths or routes intended for use by tourists.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 1, 2026, 12:56 a.m.