Triple
T16599990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heck v. Humphrey |
E403305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal civil rights case |
C14474
|
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: federal civil rights case Context triple: [Heck v. Humphrey, instanceOf, federal civil rights case]
-
A.
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.
-
B.
civil rights law
Civil rights law is the body of law that protects individuals from discrimination and unequal treatment based on characteristics such as race, gender, religion, or disability, and ensures their fundamental freedoms and equal access to opportunities.
-
C.
federal jurisdiction case
chosen
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.
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.
-
E.
civil rights site
A civil rights site is a historically or culturally significant location associated with the struggle for equal rights, justice, and the dismantling of discriminatory laws and practices.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.