Triple
T8196763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Lancaster (historic) |
E191451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime trading hub |
C7570
|
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: maritime trading hub Context triple: [Port of Lancaster (historic), instanceOf, maritime trading hub]
-
A.
transoceanic trade network
A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
-
B.
maritime trading culture
A maritime trading culture is a society whose economy, social structures, and worldview are fundamentally shaped by seafaring commerce, long-distance exchange, and coastal or port-based networks of interaction.
-
C.
Port city
chosen
A port city is an urban center located on a coast, river, or lake that serves as a hub for maritime transport, trade, and related economic and cultural activities.
-
D.
Infrastructure for trade
Infrastructure for trade encompasses the physical, digital, and institutional systems—such as transportation networks, ports, logistics hubs, communication technologies, and regulatory frameworks—that enable the efficient exchange of goods and services across regions and markets.
-
E.
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.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:42 p.m.