Triple
T32410448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Department of Justice civil rights investigation (2015) |
E828204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil rights investigation |
C59956
|
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 investigation Context triple: [U.S. Department of Justice civil rights investigation (2015), instanceOf, civil rights investigation]
-
A.
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.
-
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.
civil rights measure
A civil rights measure is a law, policy, or regulation designed to protect individuals from discrimination and ensure equal treatment and access to opportunities regardless of characteristics such as race, gender, religion, or disability.
-
D.
civil rights plaintiff
A civil rights plaintiff is an individual or entity who brings a lawsuit alleging that their legally protected civil rights have been violated by a government actor or, in some cases, a private party.
-
E.
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.
- F. None of above. chosen
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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.