Triple
T26034081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina v. EPA |
E647506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | D.C. Circuit Court of Appeals case |
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: D.C. Circuit Court of Appeals case Context triple: [North Carolina v. EPA, instanceOf, D.C. Circuit Court of Appeals case]
-
A.
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.
-
B.
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.
-
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.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.