Triple
T6263082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British opium trade in China |
E140347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | opium trade |
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: opium trade Context triple: [British opium trade in China, instanceOf, opium trade]
-
A.
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.
-
B.
transatlantic trade system
The transatlantic trade system was a network of economic exchanges linking Europe, Africa, and the Americas, involving the movement of goods, enslaved people, and raw materials across the Atlantic Ocean from the 16th to 19th centuries.
-
C.
trading empire
A trading empire is a vast, interconnected commercial domain that dominates long-distance exchange of goods, capital, and information across multiple regions or cultures, often shaping political power and economic systems in its sphere of influence.
-
D.
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.
-
E.
slave trade site
A slave trade site is a historical location where enslaved people were captured, held, bought, sold, or transported as part of the transatlantic or other slave trading systems.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:25 p.m.