Triple
T9798979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crawford v. Washington |
E237787
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confrontation Clause case |
C2807
|
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: Confrontation Clause case Context triple: [Crawford v. Washington, instanceOf, Confrontation Clause case]
-
A.
Sixth Amendment case
chosen
A Sixth Amendment case is a legal dispute in which a court interprets or applies the constitutional rights of criminal defendants to counsel, a speedy and public trial, an impartial jury, confrontation of witnesses, compulsory process, and notice of accusations.
-
B.
constitutional law case
A constitutional law case is a legal dispute that requires a court to interpret and apply a nation's constitution to determine the validity of government actions, laws, or policies.
-
C.
free speech case
A free speech case is a legal dispute that centers on whether an individual’s or group’s expression is protected under constitutional or statutory guarantees of freedom of speech.
-
D.
civil rights era case
A civil rights era case is a legal dispute, typically from the mid-20th century United States, that addresses issues of racial segregation, discrimination, or the protection and expansion of civil liberties and equal rights under the law.
-
E.
criminal syndicalism case
A criminal syndicalism case is a legal proceeding in which individuals or groups are prosecuted for advocating, teaching, or organizing actions—often involving violence or sabotage—aimed at overthrowing or disrupting established government or industrial systems.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:28 p.m.