Triple
T18014070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alleghany Highlands |
E430955
|
entity |
| Predicate | hasScenicByways |
P13952
|
FINISHED |
| Object | mountain roads |
—
|
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: mountain roads | Statement: [Alleghany Highlands, hasScenicByways, mountain roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicByways Context triple: [Alleghany Highlands, hasScenicByways, mountain roads]
-
A.
hasScenicByway
chosen
Indicates that one place, route, or area is connected to or includes a designated scenic byway.
-
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.
hasScenicDrive
Indicates that one entity offers or features a visually appealing or picturesque driving route associated with it.
-
D.
hasScenicSections
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
E.
hasScenicPullouts
Indicates that a route or roadway includes designated scenic pullout areas where travelers can stop to view the 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b521befc81908dff44f19aa3d580 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.