Triple
T8740638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molasses Act 1733 |
E207490
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British colonial trade law |
C766
|
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: British colonial trade law Context triple: [Molasses Act 1733, instanceOf, British colonial trade law]
-
A.
British colonial law
chosen
British colonial law refers to the legal systems, statutes, and judicial practices imposed by Britain on its colonies, designed to maintain imperial control while selectively incorporating or reshaping local customs and institutions.
-
B.
British colonial position
A British colonial position is an official role or office established by the British Empire to administer, govern, or oversee territories and populations under colonial rule.
-
C.
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.
-
D.
British overseas presence in China
The conceptual class "British overseas presence in China" encompasses the political, economic, military, and cultural activities, institutions, and influences established by Britain within Chinese territory from the early modern period through the end of formal imperial involvement.
-
E.
English colonial settlement
An English colonial settlement is a community established by England in foreign territories during the age of exploration and empire, serving as a base for resource extraction, trade, and cultural expansion.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.