Triple
T28253478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sierra Crest |
E712376
|
entity |
| Predicate | traversedNearBy |
P12052
|
FINISHED |
| Object | John Muir Trail |
—
|
NE NERFINISHED |
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: John Muir Trail | Statement: [Sierra Crest, traversedNearBy, John Muir Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversedNearBy Context triple: [Sierra Crest, traversedNearBy, John Muir Trail]
-
A.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
B.
hasNearbyTrail
chosen
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
D.
hasNearbyTrailFeature
Indicates that one entity has another entity as a trail-related feature located in close physical proximity.
-
E.
navigatedAround
Indicates that one entity moved in such a way as to go past or circumvent another entity or obstacle without directly passing through or over it.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 11:06 p.m.