Triple
T10430681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brzonkala v. Virginia Polytechnic Institute and State University |
E245904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil rights lawsuit |
C26453
|
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 lawsuit Context triple: [Brzonkala v. Virginia Polytechnic Institute and State University, instanceOf, civil rights lawsuit]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
civil rights document
A civil rights document is an official record or legal instrument that defines, asserts, or protects individuals’ fundamental freedoms and equal treatment under the law.
-
E.
civil rights event
chosen
A civil rights event is a public occurrence—such as a protest, march, rally, meeting, or legal action—organized to challenge discrimination and advocate for equal rights and social justice for marginalized groups.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:13 p.m.