Triple
T23076388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stourport Basins |
E575341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic inland port |
C5917
|
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 inland port Context triple: [Stourport Basins, instanceOf, historic inland port]
-
A.
inland port
chosen
An inland port is a logistics and transportation hub located away from coastal seaports, typically along rivers, canals, or rail corridors, that facilitates the transfer, storage, and distribution of goods between different modes of transport.
-
B.
historic harbor
A historic harbor is a waterfront area that has played a significant role in maritime trade, travel, or defense over time and retains physical or cultural features reflecting its past.
-
C.
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.
-
D.
former port city
A former port city is an urban settlement that once functioned as a significant maritime trade hub but has since lost its port operations or primary seafaring role due to economic, environmental, or infrastructural changes.
-
E.
historic wharf
A historic wharf is a preserved waterfront structure once used for docking, loading, and unloading ships, now valued for its cultural, architectural, and maritime heritage significance.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:56 p.m.