Triple
T28054552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court decree in Arizona v. California |
E708925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Supreme Court decree |
C4529
|
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 Supreme Court decree Context triple: [Supreme Court decree in Arizona v. California, instanceOf, United States Supreme Court decree]
-
A.
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.
-
B.
court decision
chosen
A court decision is a formal, authoritative ruling issued by a judicial body that resolves the legal issues in a case and may establish or apply legal precedent.
-
C.
Supreme Court justice
A Supreme Court justice is a high-ranking judicial official who serves on the nation’s highest court, interpreting the constitution and resolving the most significant legal disputes.
-
D.
United States Supreme Court case
A United States Supreme Court case is a legal dispute brought before the highest federal court in the U.S., resulting in a binding decision that interprets the Constitution, federal laws, or treaties and sets nationwide precedent.
-
E.
legal decree
A legal decree is an authoritative, formal order issued by a governmental or judicial body that has the force of law and mandates specific actions, rights, or obligations.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:35 p.m.