Triple
T9160264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawksbill Mountain |
E219801
|
entity |
| Predicate | hasLoopHikeDistance |
P35279
|
FINISHED |
| Object | approximately 2.9 miles |
—
|
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: approximately 2.9 miles | Statement: [Hawksbill Mountain, hasLoopHikeDistance, approximately 2.9 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoopHikeDistance Context triple: [Hawksbill Mountain, hasLoopHikeDistance, approximately 2.9 miles]
-
A.
hikeLength
Indicates the distance or duration associated with a hiking activity or trail.
-
B.
approximateRoundTripDistanceFromTrailhead
chosen
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
C.
approximateHikeTimeRoundTrip
Indicates the estimated total time required to complete a hike from the starting point to the destination and back to the start.
-
D.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
E.
hasCyclingDistance
Indicates that there is a specified distance associated with traveling between entities by cycling.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d953c081908d21f363801aaae4 |
completed | April 1, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.