Triple
T22076138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sajjan Singh v. State of Rajasthan |
E545526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Supreme Court case |
C26724
|
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 Supreme Court case Context triple: [Sajjan Singh v. State of Rajasthan, instanceOf, Indian Supreme Court case]
-
A.
Supreme Court of India case
chosen
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.
Canadian court case
A Canadian court case is a formal legal proceeding in which disputes or criminal charges are adjudicated by a court within Canada’s judicial system, resulting in a binding decision based on Canadian law.
-
C.
bench of the Bombay High Court
A bench of the Bombay High Court is a panel of one or more judges of the court constituted to hear and decide specific cases or categories of matters within its jurisdiction.
-
D.
supreme court
The Supreme Court is the highest judicial authority in a legal system, responsible for interpreting the constitution, resolving significant legal disputes, and setting binding precedents for lower courts.
-
E.
case of the Permanent Court of International Justice
A case of the Permanent Court of International Justice is a formal international legal dispute submitted to and adjudicated by the PCIJ, resulting in a binding judgment or advisory opinion on issues of international law between states or international entities.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.