Triple
T34068374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Payson Canyon |
E873695
|
entity |
| Predicate | hasScenicDesignationNearby |
P117799
|
FINISHED |
| Object | Nebo Loop National Scenic Byway |
—
|
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: Nebo Loop National Scenic Byway | Statement: [Payson Canyon, hasScenicDesignationNearby, Nebo Loop National Scenic Byway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicDesignationNearby Context triple: [Payson Canyon, hasScenicDesignationNearby, Nebo Loop National Scenic Byway]
-
A.
hasNearbyStatePark
Indicates that a location is situated close to at least one designated state park.
-
B.
hasScenicDesignationSince
Indicates that an entity has held an official scenic designation continuously since a specified date.
-
C.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
-
D.
hasScenicPassNearby
chosen
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
E.
nearbyProtectedSite
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:52 a.m.