Triple
T1446123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Coordination and Compliance Section |
E31181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil rights enforcement office |
C3027
|
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 enforcement office Context triple: [Federal Coordination and Compliance Section, instanceOf, civil rights enforcement office]
-
A.
civil rights enforcement agency
chosen
A civil rights enforcement agency is a governmental or independent body responsible for investigating discrimination complaints, enforcing civil rights laws, and promoting equal protection and fair treatment for all individuals.
-
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 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.
-
D.
justice ministry
A justice ministry is a government department responsible for overseeing the legal system, including courts, prosecution, correctional services, and the development and implementation of justice-related policies and legislation.
-
E.
county district attorney office
The county district attorney office is a government legal agency responsible for prosecuting criminal cases on behalf of the public within a specific county jurisdiction.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.