Triple
T5219828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Daylight |
E117842
|
entity |
| Predicate | scenicSection |
P35458
|
FINISHED |
| Object | Santa Barbara to San Luis Obispo |
—
|
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: Santa Barbara to San Luis Obispo | Statement: [Coast Daylight, scenicSection, Santa Barbara to San Luis Obispo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenicSection Context triple: [Coast Daylight, scenicSection, Santa Barbara to San Luis Obispo]
-
A.
hasScenicSections
chosen
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
B.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
C.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
D.
hasScenicValue
Indicates that something possesses notable aesthetic or visual appeal, often due to its natural beauty or pleasing surroundings.
-
E.
isScenicByway
Indicates that a roadway is officially designated as a scenic byway, recognized for its notable visual, cultural, or natural appeal along its route.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ab6e63c8190964b2b65a0206134 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.