Triple
T17637356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 180 |
E430129
|
entity |
| Predicate | isScenicIn |
P41742
|
FINISHED |
| Object | Sierra Nevada section |
—
|
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: Sierra Nevada section | Statement: [California State Route 180, isScenicIn, Sierra Nevada section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScenicIn Context triple: [California State Route 180, isScenicIn, Sierra Nevada section]
-
A.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
-
B.
isScenicTown
Indicates that a town is visually attractive or picturesque, often due to its natural surroundings, architecture, or overall aesthetic appeal.
-
C.
isPartOfScenicVista
chosen
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
D.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
E.
hasScenicValue
Indicates that something possesses notable aesthetic or visual appeal, often due to its natural beauty or pleasing surroundings.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de1e0888190a3c8bbd451aed2fb |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.