Triple
T33026459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Sea trade network |
E845055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient trade network |
C3246
|
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: ancient trade network Context triple: [Red Sea trade network, instanceOf, ancient trade network]
-
A.
ancient trade route
An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
-
B.
transoceanic trade network
chosen
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.
-
C.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
D.
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.
-
E.
colonial-era trade corridor
A colonial-era trade corridor is a strategically established route or network used during colonial times to transport goods, people, and resources between colonies and imperial centers, shaping economic patterns and cultural exchanges.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.