Triple
T22396577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S. S. Dhanoa v. Union of India |
E553646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian constitutional law case |
C734
|
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 constitutional law case Context triple: [S. S. Dhanoa v. Union of India, instanceOf, Indian constitutional law case]
-
A.
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.
-
B.
constitutional law case
chosen
A constitutional law case is a legal dispute that requires a court to interpret and apply a nation's constitution to determine the validity of government actions, laws, or policies.
-
C.
Indian jurist
An Indian jurist is a legal expert from India who interprets, analyzes, and applies the law through roles such as judge, legal scholar, or senior advocate within the Indian legal system.
-
D.
Indian regulation
Indian regulation refers to the body of laws, rules, and guidelines enacted by Indian legislative, executive, and regulatory authorities to govern economic, social, and administrative activities within the country.
-
E.
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.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.