Triple
T22317727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Washington |
E551693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Indian law case |
C11697
|
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: United States Indian law case Context triple: [United States v. Washington, instanceOf, United States Indian law case]
-
A.
Native American law
chosen
Native American law is the body of federal, state, and tribal legal principles governing the rights, sovereignty, lands, resources, and governance of Native American tribes and their members.
-
B.
Native American civil rights action
Native American civil rights action is organized legal, political, and grassroots efforts by Indigenous peoples and their allies to secure sovereignty, protect treaty rights, and achieve equal treatment under U.S. law and society.
-
C.
United States state court case
A United States state court case is a legal dispute adjudicated within a state’s judicial system, governed by that state’s laws and procedures rather than federal law.
-
D.
Aboriginal law case
An Aboriginal law case is a legal dispute or judicial decision that interprets and applies laws, rights, and obligations relating to Indigenous peoples, their lands, cultures, and governance.
-
E.
Aboriginal rights case
An Aboriginal rights case is a legal proceeding that addresses claims by Indigenous peoples to inherent or treaty-based rights, such as land, resources, self-governance, or cultural practices, and determines how those rights are recognized and protected under state law.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.