Triple
T1439830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Tennessee v. John Thomas Scopes |
E31044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States state court case |
C6650
|
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 state court case Context triple: [State of Tennessee v. John Thomas Scopes, instanceOf, United States state court case]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
United States legal history event
A United States legal history event is a significant occurrence—such as a court decision, statute, constitutional amendment, or legal controversy—that materially shaped the development, interpretation, or application of American law.
-
E.
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.
- F. None of above. chosen
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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.