Triple
T12072558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Support for the Civil Rights Act reauthorizations |
E287459
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil rights advocacy |
C11125
|
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 advocacy Context triple: [Support for the Civil Rights Act reauthorizations, instanceOf, civil rights advocacy]
-
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 pioneer
A civil rights pioneer is an individual who courageously challenges systemic injustice and discrimination, leading transformative efforts to secure equal rights and freedoms for marginalized groups.
-
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 event
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.
-
E.
civil rights movement organization
chosen
A civil rights movement organization is a group formed to advocate for and advance the legal, social, and political rights of marginalized or oppressed communities through coordinated activism, education, and policy change.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:48 p.m.