Triple
T2124005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernal Fall Footbridge |
E43989
|
entity |
| Predicate | trailDistanceFromTrailhead |
P32541
|
FINISHED |
| Object | about 0.8 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: about 0.8 miles one way | Statement: [Vernal Fall Footbridge, trailDistanceFromTrailhead, about 0.8 miles one way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceFromTrailhead Context triple: [Vernal Fall Footbridge, trailDistanceFromTrailhead, about 0.8 miles one way]
-
A.
trekDistanceFromRoadHead
chosen
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
-
B.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
C.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
D.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
-
E.
longDistanceTrail
Indicates that a trail or route spans a considerable distance, typically intended for extended or multi-day travel.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb55cb2c8190aab8199da3335032 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.