Triple
T4215680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokopah Falls |
E94208
|
entity |
| Predicate | approxTrailDistanceOneWay |
P18078
|
FINISHED |
| Object | about 1.7 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: about 1.7 miles | Statement: [Tokopah Falls, approxTrailDistanceOneWay, about 1.7 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxTrailDistanceOneWay Context triple: [Tokopah Falls, approxTrailDistanceOneWay, about 1.7 miles]
-
A.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
B.
hasApproximateDrivingDistanceFrom
Indicates that one entity is located at an estimated or approximate driving distance from another entity, typically measured along road routes rather than as a precise or exact value.
-
C.
trailLengthApprox
chosen
Indicates an approximate measurement of the total length of a trail.
-
D.
trekDistanceFromRoadHead
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
-
E.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.