Triple
T34004269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebo Loop Scenic Byway |
E871915
|
entity |
| Predicate | stateScenicBywayStatus |
P133906
|
FINISHED |
| Object | Utah 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: Utah Scenic Byway | Statement: [Nebo Loop Scenic Byway, stateScenicBywayStatus, Utah Scenic Byway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateScenicBywayStatus Context triple: [Nebo Loop Scenic Byway, stateScenicBywayStatus, Utah Scenic Byway]
-
A.
stateScenicBywayProgram
chosen
Indicates that a route or roadway is designated or managed under a state-level scenic byway program.
-
B.
isScenicByway
Indicates that a roadway is officially designated as a scenic byway, recognized for its notable visual, cultural, or natural appeal along its route.
-
C.
scenicDesignationStatus
Indicates the formal status or classification of an entity regarding its recognition or protection as a scenic or visually significant area or route.
-
D.
hasScenicByway
Indicates that one place, route, or area is connected to or includes a designated scenic byway.
-
E.
stateScenicRiverDesignation
Indicates that a river or river segment has been officially designated by a state as part of its scenic river system or program.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 1, 2026, 1:50 a.m.