Triple
T11525216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onion Valley trailhead |
E273275
|
entity |
| Predicate | trailDirectionFromTrailhead |
P76664
|
FINISHED |
| Object | west toward Kearsarge Pass |
—
|
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: west toward Kearsarge Pass | Statement: [Onion Valley trailhead, trailDirectionFromTrailhead, west toward Kearsarge Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDirectionFromTrailhead Context triple: [Onion Valley trailhead, trailDirectionFromTrailhead, west toward Kearsarge Pass]
-
A.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
B.
routeDirectionB
chosen
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
C.
travelsDirection
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
D.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
E.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd379648190b342e0c4b4f685b7 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.