Triple
T16451695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson v. Memphis & Charleston Railroad Company |
E399566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil Rights Cases (1883) |
C34134
|
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: Civil Rights Cases (1883) Context triple: [Robinson v. Memphis & Charleston Railroad Company, instanceOf, Civil Rights Cases (1883)]
-
A.
United States slavery case
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
chosen
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.
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.
-
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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.