Triple
T30281543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooker Falls Access Area |
E770106
|
entity |
| Predicate | trailDistanceTo |
P32541
|
FINISHED |
| Object | Hooker Falls |
—
|
NE NERFINISHED |
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: Hooker Falls | Statement: [Hooker Falls Access Area, trailDistanceTo, Hooker Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceTo Context triple: [Hooker Falls Access Area, trailDistanceTo, Hooker Falls]
-
A.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
-
B.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
C.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
D.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
E.
trekDistanceFromRoadHead
chosen
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681057b688190b8058e4cd2b2235a |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:45 p.m.