Triple

T36506132
Position Surface form Disambiguated ID Type / Status
Subject Swift River E899465 entity
Predicate hasNearbyHighwayScenicByway P13952 FINISHED
Object Kancamagus 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: Kancamagus Scenic Byway | Statement: [Swift River, hasNearbyHighwayScenicByway, Kancamagus Scenic Byway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyHighwayScenicByway
Context triple: [Swift River, hasNearbyHighwayScenicByway, Kancamagus Scenic Byway]
  • 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. hasScenicSectionNear
    Indicates that one location includes a visually appealing or picturesque segment situated close to another specified location.
  • D. isScenicRouteOnWayTo
    Indicates that a particular route is visually appealing and lies along the path between a starting point and a destination.
  • E. hasScenicRoutes
    Indicates that one location, path, or area offers routes that are visually attractive or notable for their natural or aesthetic scenery.
  • 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_69f76e5b92088190933afda3f7531dd4 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a005d878aec81908e1177914a8fb610 completed May 10, 2026, 10:27 a.m.
PD Predicate disambiguation batch_6a005c382f8881908ff33ebb7f88c430 completed May 10, 2026, 10:21 a.m.
Created at: May 3, 2026, 4:10 p.m.