Triple
T37142085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia v. West Virginia |
E920140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal dispute between U.S. states |
C35018
|
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: legal dispute between U.S. states Context triple: [Virginia v. West Virginia, instanceOf, legal dispute between U.S. states]
-
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 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 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.
-
D.
legal controversy
chosen
A legal controversy is a dispute between parties over rights, obligations, or facts that is brought within a legal system for resolution.
-
E.
American Civil War legal case
An American Civil War legal case is a judicial proceeding arising during or in the aftermath of the Civil War that addresses issues such as military authority, civil liberties, property rights, or the constitutional limits of federal and state power in wartime.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.