Triple
T25466733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairview Canyon |
E638194
|
entity |
| Predicate | isPartOfScenicByway |
P13952
|
FINISHED |
| Object | Huntington Canyon 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: Huntington Canyon Scenic Byway | Statement: [Fairview Canyon, isPartOfScenicByway, Huntington Canyon Scenic Byway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfScenicByway Context triple: [Fairview Canyon, isPartOfScenicByway, Huntington Canyon Scenic Byway]
-
A.
isScenicByway
Indicates that a roadway is officially designated as a scenic byway, recognized for its notable visual, cultural, or natural appeal along its route.
-
B.
hasScenicByway
chosen
Indicates that one place, route, or area is connected to or includes a designated scenic byway.
-
C.
stateScenicBywayProgram
Indicates that a route or roadway is designated or managed under a state-level scenic byway program.
-
D.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
E.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 2:15 p.m.