Triple
T11826000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specific Relief Act 1877 |
E281261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Indian 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 Indian statute Context triple: [Specific Relief Act 1877, instanceOf, British Indian 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 India
An Act of Parliament of India is a formal written law enacted by the Indian Parliament through its legislative process, which becomes legally binding upon receiving presidential assent and publication.
-
C.
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.
-
D.
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.
-
E.
presidency of British India
The presidency of British India was a major administrative division governed by the British East India Company and later the British Crown, serving as a regional center of political, military, and economic control.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.