Triple
T5083722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annulment of Partition of Bengal 1911 |
E114584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British colonial policy change |
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: British colonial policy change Context triple: [Annulment of Partition of Bengal 1911, instanceOf, British colonial policy change]
-
A.
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.
-
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 policy conference
A colonial policy conference is a formal gathering of scholars, policymakers, and stakeholders to analyze, debate, and shape understandings of past and present colonial governance and its enduring impacts.
-
D.
colonialism
Colonialism is a system of domination in which a powerful state extends control over foreign territories and peoples, exploiting their resources, labor, and cultures for economic and political gain.
-
E.
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.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:39 p.m.