Triple
T11301295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Parkways (Buffalo, New York) |
E267595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic parkway system |
C1081
|
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: historic parkway system Context triple: [The Parkways (Buffalo, New York), instanceOf, historic parkway system]
-
A.
historic park system
A historic park system is a coordinated network of parks, landscapes, and related sites preserved and managed to protect, interpret, and provide public access to places of significant historical, cultural, and architectural value.
-
B.
historic road
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
C.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
-
D.
historic transportation system
chosen
A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
-
E.
United States National Historic Trail
A United States National Historic Trail is a federally designated long-distance route that commemorates and protects significant historical travel paths, events, and landscapes across the nation.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.