Triple
T37346876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casper Mountain |
E927198
|
entity |
| Predicate | hasScenicOverlookOf |
P9193
|
FINISHED |
| Object | North Platte River valley |
—
|
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: North Platte River valley | Statement: [Casper Mountain, hasScenicOverlookOf, North Platte River valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicOverlookOf Context triple: [Casper Mountain, hasScenicOverlookOf, North Platte River valley]
-
A.
hasScenicViewOf
chosen
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
B.
hasScenicAccessTo
Indicates that one place or object provides a visually appealing or notable view of another place or object.
-
C.
hasScenicViewpoints
Indicates that something includes or provides locations specifically intended for enjoying scenic or panoramic views.
-
D.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
E.
hasScenicSectionAt
Indicates that a route, path, or area contains a specific segment or location that is considered scenic at that point.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:16 p.m.