Triple
T38609710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bailey v. Alabama |
E934443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Thirteenth Amendment case |
C29520
|
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: Thirteenth Amendment case Context triple: [Bailey v. Alabama, instanceOf, Thirteenth Amendment case]
-
A.
United States slavery case
chosen
A United States slavery case is a legal dispute, historical or contemporary, that addresses the status, treatment, or legacy of enslaved persons within the jurisdiction of U.S. law.
-
B.
Reconstruction-era case
A Reconstruction-era case is a legal dispute arising during the post–Civil War period (circa 1865–1877) that addresses issues related to federal authority, civil rights, and the reintegration of former Confederate states into the Union.
-
C.
Sixth Amendment case
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.
-
D.
fugitive slave case
A fugitive slave case is a legal proceeding in which an enslaved person who has escaped from a slaveholding jurisdiction is pursued, captured, and adjudicated under laws governing the return of escaped slaves.
-
E.
fugitive slave law case
A fugitive slave law case is a legal proceeding arising from the capture, return, or status of an escaped enslaved person under statutes mandating the recovery of individuals fleeing enslavement.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.