Triple
T31724754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berry Creek Falls |
E809680
|
entity |
| Predicate | trailDistanceFromParkHQ |
P63487
|
FINISHED |
| Object | approximately 10 miles round trip |
—
|
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 10 miles round trip | Statement: [Berry Creek Falls, trailDistanceFromParkHQ, approximately 10 miles round trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceFromParkHQ Context triple: [Berry Creek Falls, trailDistanceFromParkHQ, approximately 10 miles round trip]
-
A.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
-
B.
trailDistanceApprox
chosen
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
C.
distanceToNationalParkVillage
Indicates the measured distance between a given place and the nearest national park village.
-
D.
directionFromParkCenter
Indicates the compass direction or relative bearing of an entity when measured outward from the center point of a park.
-
E.
tourLength
Indicates the total duration or distance covered by a tour or route.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aafaf65c8190a39e18111e02622a |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:19 p.m.