Triple
T30924767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compensation and Reparation Authority |
E787826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reparations institution |
C44832
|
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: reparations institution Context triple: [Compensation and Reparation Authority, instanceOf, reparations institution]
-
A.
reparations support office
chosen
A reparations support office is an organization that assists individuals and communities in understanding, accessing, and managing reparative justice programs, including claims, documentation, advocacy, and related support services.
-
B.
re-education facility
A re-education facility is an institution designed to reshape individuals’ beliefs, behaviors, or skills—often through structured instruction, counseling, and controlled environments—so they conform to specific social, political, or rehabilitative goals.
-
C.
reparations law
Reparations law is the body of legal principles and mechanisms that govern how individuals, groups, or states are compensated or otherwise remedied for historical or contemporary injustices and harms.
-
D.
county institution
A county institution is an organization or facility established and operated by a county government to provide public services, administration, or regulation within its jurisdiction.
-
E.
eugenic institution
A eugenic institution is an organization or establishment designed to promote, enforce, or research policies and practices aimed at shaping the genetic composition of a population, often through discriminatory or coercive means.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.