Triple
T10780249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Courts Act 1861 |
E254299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian judicial reform statute |
C3124
|
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: Indian judicial reform statute Context triple: [High Courts Act 1861, instanceOf, Indian judicial reform statute]
-
A.
judicial reform law
chosen
A judicial reform law is legislation that restructures the organization, powers, procedures, or accountability mechanisms of a court system to improve its fairness, efficiency, independence, or accessibility.
-
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.
Indian criminal law
Indian criminal law is the body of legal rules, primarily codified in statutes like the Indian Penal Code and the Code of Criminal Procedure, that defines criminal offenses, prescribes punishments, and regulates the investigation, prosecution, and adjudication of crimes in India.
-
D.
Supreme Court of India case
A Supreme Court of India case is a legal dispute or matter formally brought before the Supreme Court of India for authoritative interpretation of law, constitutional adjudication, or final appellate review.
-
E.
legal reform
Legal reform is the process of reviewing, amending, and modernizing laws and legal institutions to better reflect current societal values, address injustices, and improve the effectiveness of the legal system.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:17 p.m.