Triple
T4215681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokopah Falls |
E94208
|
entity |
| Predicate | approxTrailDistanceRoundTrip |
P35279
|
FINISHED |
| Object | about 3.4 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 3.4 miles | Statement: [Tokopah Falls, approxTrailDistanceRoundTrip, about 3.4 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxTrailDistanceRoundTrip Context triple: [Tokopah Falls, approxTrailDistanceRoundTrip, about 3.4 miles]
-
A.
approximateRoundTripDistanceFromTrailhead
chosen
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
B.
approximateHikeTimeRoundTrip
Indicates the estimated total time required to complete a hike from the starting point to the destination and back to the start.
-
C.
numberOfDailyRoundTrips
Indicates the total count of round-trip journeys performed per day in the described context.
-
D.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
E.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
- 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.