Triple
T825921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ming and Qing Chinese maritime trade restrictions |
E17852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese imperial policy |
C6128
|
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: Chinese imperial policy Context triple: [Ming and Qing Chinese maritime trade restrictions, instanceOf, Chinese imperial policy]
-
A.
colonial policy
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.
-
B.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
C.
Japanese imperial office
A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
-
D.
policy of the Soviet Union
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
-
E.
expansionist doctrine
An expansionist doctrine is a belief system or policy framework that justifies and promotes the territorial, economic, or political enlargement of a state or group, often at the expense of others.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.