Triple
T6508375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigation Acts (England) |
E150067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial trade regulation |
C1297
|
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: colonial trade regulation Context triple: [Navigation Acts (England), instanceOf, colonial trade regulation]
-
A.
colonial enterprise
A colonial enterprise is an organized venture, typically led by a state or chartered company, that establishes control over foreign territories and peoples to extract resources, labor, and strategic advantage.
-
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.
colonial policy
chosen
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
-
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.
colonial order
A colonial order is a hierarchical system of political, economic, and cultural domination in which an external power controls and structures the institutions, resources, and social relations of a colonized territory to serve imperial interests.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:43 p.m.