Triple
T35020242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idaho State Highway 21 |
E1010172
|
entity |
| Predicate | isPartOfScenicBywaySystem |
P13952
|
FINISHED |
| Object | Idaho scenic byways |
—
|
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: Idaho scenic byways | Statement: [Idaho State Highway 21, isPartOfScenicBywaySystem, Idaho scenic byways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfScenicBywaySystem Context triple: [Idaho State Highway 21, isPartOfScenicBywaySystem, Idaho scenic byways]
-
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.
isPartOfTrailSystem
Indicates that something belongs to, or is included within, a larger trail network or trail system.
-
D.
stateScenicBywayProgram
Indicates that a route or roadway is designated or managed under a state-level scenic byway program.
-
E.
hasWildAndScenicDesignation
Indicates that an area or waterway has been formally designated under a Wild and Scenic protection status.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.