Triple
T20054953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elfin Lakes Trail |
E499302
|
entity |
| Predicate | approximateHikingTimeRoundTrip |
P32784
|
FINISHED |
| Object | 6 to 8 hours |
—
|
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: 6 to 8 hours | Statement: [Elfin Lakes Trail, approximateHikingTimeRoundTrip, 6 to 8 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateHikingTimeRoundTrip Context triple: [Elfin Lakes Trail, approximateHikingTimeRoundTrip, 6 to 8 hours]
-
A.
approximateHikeTimeRoundTrip
chosen
Indicates the estimated total time required to complete a hike from the starting point to the destination and back to the start.
-
B.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
C.
recommendedTimeToHike
Indicates the suggested or optimal time period during which one should undertake a particular hike.
-
D.
hikeLength
Indicates the distance or duration associated with a hiking activity or trail.
-
E.
approximateTripDuration
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66332b300819097f5dca1636e5822 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.