Triple
T17374471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miller v. Johnson |
E422400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | racial gerrymandering case |
C36303
|
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: racial gerrymandering case Context triple: [Miller v. Johnson, instanceOf, racial gerrymandering case]
-
A.
redistricting case
chosen
A redistricting case is a legal dispute challenging how electoral district boundaries are drawn, typically alleging violations of constitutional or statutory rules governing fair representation.
-
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.
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.
school segregation case
A school segregation case is a legal dispute challenging the separation of students into different schools or classrooms based on race or related factors, typically alleging violations of equal protection or civil rights laws.
-
E.
redistricting cycle
A redistricting cycle is the recurring process, typically following a census, in which electoral district boundaries are reviewed and redrawn to reflect population changes and maintain fair representation.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.