Triple
T12399202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Supreme Court cases |
E296202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal case law |
C29175
|
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 federal case law Context triple: [United States Supreme Court cases, instanceOf, United States federal case law]
-
A.
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.
-
B.
United States federal law
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
-
C.
United States Court of Appeals case
chosen
A United States Court of Appeals case is a federal appellate court decision that reviews and resolves legal issues appealed from U.S. district courts or certain federal agencies within its circuit jurisdiction.
-
D.
United States state law
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
-
E.
federal jurisdiction case
A federal jurisdiction case is a legal dispute that is heard in a federal court because it involves federal laws, the U.S. Constitution, the federal government, or parties from different states meeting specific jurisdictional requirements.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:54 p.m.