Triple
T37605007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Mediterranean Punic world |
E935625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime trading network |
C65899
|
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 network Context triple: [Western Mediterranean Punic world, instanceOf, maritime trading network]
-
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 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.
-
C.
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.
-
D.
maritime trading centre
A maritime trading centre is a coastal hub where goods, services, and information are exchanged via sea routes, integrating port infrastructure, commercial activities, and logistics networks to facilitate regional and international trade.
-
E.
inter-island trade network
An inter-island trade network is a system of economic, logistical, and social relationships that facilitates the exchange of goods, services, and information among multiple islands.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.