Triple
T25919454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copperhouse and Hayle Harbour |
E653127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime trading centre |
C50088
|
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 centre Context triple: [Copperhouse and Hayle Harbour, instanceOf, maritime trading centre]
-
A.
maritime trade exchange
A maritime trade exchange is a structured marketplace or platform where participants buy, sell, and negotiate shipping services, cargo space, and related maritime trade instruments under defined rules and standards.
-
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.
medieval trading colony
A medieval trading colony is a distant settlement established and controlled by a city or state to facilitate long-distance commerce, resource extraction, and cultural exchange through permanent mercantile presence.
-
D.
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.
-
E.
Swahili trading city
A Swahili trading city is a coastal urban center along the East African littoral that thrived as a hub of maritime commerce, cultural exchange, and Islamic influence, linking African hinterlands with the Indian Ocean world.
- F. None of above. chosen
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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:32 a.m.