Triple
T33956645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Scenic Byway |
E870590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-designated scenic byway network |
C42446
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: state-designated scenic byway network Context triple: [New Jersey Scenic Byway, instanceOf, state-designated scenic byway network]
-
A.
scenic byway
A scenic byway is a designated roadway recognized for its exceptional natural, cultural, historic, or recreational qualities, offering travelers a visually and experientially rich driving route.
-
B.
scenic highway designation program
chosen
A scenic highway designation program is an initiative that identifies, evaluates, and officially recognizes roadways with exceptional natural, cultural, or historic visual qualities to promote preservation, tourism, and context-sensitive development.
-
C.
state scenic corridor
A state scenic corridor is a designated roadway or linear area recognized and protected by a state for its outstanding natural, cultural, or visual qualities, often with special regulations to preserve its scenic character.
-
D.
National Scenic Trail
A National Scenic Trail is a federally designated long-distance trail that offers outstanding recreational opportunities and showcases significant natural, scenic, and cultural landscapes across large geographic areas.
-
E.
National Tourist Route
A National Tourist Route is a designated roadway or travel corridor recognized for its exceptional scenic, cultural, and recreational value, developed and managed to enhance visitor experiences and promote regional tourism.
- F. None of above.
Provenance (1 batch)
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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.