Triple
T20396001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Peak Junction |
E500205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic transport interchange |
C3667
|
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 transport interchange Context triple: [High Peak Junction, instanceOf, historic transport interchange]
-
A.
historic transportation system
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.
-
B.
historic intersection
A historic intersection is a crossroads or junction that has significant cultural, social, or political importance due to notable events, architecture, or long-standing community activity that occurred or developed there.
-
C.
historic infrastructure
chosen
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
-
D.
historic entrance
A historic entrance is a formally recognized point of access to a building or site that embodies significant architectural, cultural, or historical value from a particular period.
-
E.
historic portage route
A historic portage route is a traditional overland path used to carry watercraft and goods between navigable waterways, often significant for its cultural, economic, and transportation history.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.