Triple
T2257148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Yosemite Fall Trail |
E49752
|
entity |
| Predicate | parkingNearby |
P28492
|
FINISHED |
| Object | Yosemite Falls parking area |
—
|
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: Yosemite Falls parking area | Statement: [Lower Yosemite Fall Trail, parkingNearby, Yosemite Falls parking area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkingNearby Context triple: [Lower Yosemite Fall Trail, parkingNearby, Yosemite Falls parking area]
-
A.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
B.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
-
C.
nearbyVenue
chosen
Indicates that one venue is located close to another venue in physical space.
-
D.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
-
E.
parkingType
Indicates the specific kind or category of parking arrangement associated with an entity (e.g., street, garage, lot, reserved).
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1570dc88190bb2b17ed4c25dbb5 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.