Triple
T32399228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sand Point |
E827896
|
entity |
| Predicate | trailDistanceFromOzetteTrailhead |
P63487
|
FINISHED |
| Object | approximately 3 miles one way |
—
|
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 3 miles one way | Statement: [Sand Point, trailDistanceFromOzetteTrailhead, approximately 3 miles one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceFromOzetteTrailhead Context triple: [Sand Point, trailDistanceFromOzetteTrailhead, approximately 3 miles one way]
-
A.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
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.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
-
D.
trailDistanceFromCrescentMeadow
Indicates the length of a trail measured from Crescent Meadow as the starting reference point.
-
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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c21961388190be9a7c535ed25761 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:52 a.m.