Triple
T32273619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Emigration Act 1842 |
E824482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British colonial statute |
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 statute Context triple: [Indian Emigration Act 1842, instanceOf, British colonial statute]
-
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.
Act of Parliament of the United Kingdom
An Act of Parliament of the United Kingdom is a formal law enacted by the UK Parliament, comprising the House of Commons, the House of Lords, and the monarch, which has legal force throughout its applicable jurisdictions.
-
C.
Act of Parliament of England
An Act of Parliament of England is a formal written law enacted by the English Parliament prior to the 1707 Acts of Union, having legal force within the Kingdom of England and its territories.
-
D.
Parliamentary statute
A parliamentary statute is a formal written law enacted by a legislative body that establishes, modifies, or regulates legal rights, duties, or procedures within its jurisdiction.
-
E.
British colonial residency
A British colonial residency was an official administrative and diplomatic establishment where a British Resident lived and worked to oversee, advise, and often indirectly control the affairs of a princely state or protectorate within the British Empire.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:42 a.m.