Triple
T35952883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation B |
E1039777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-discrimination regulation |
C31860
|
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: anti-discrimination regulation Context triple: [Regulation B, instanceOf, anti-discrimination regulation]
-
A.
anti-discrimination measure
An anti-discrimination measure is a policy, law, or practice designed to prevent, reduce, or remedy unequal treatment of individuals or groups based on protected characteristics such as race, gender, age, disability, religion, or sexual orientation.
-
B.
anti-discrimination measure
An anti-discrimination measure is a policy, law, or action designed to prevent, reduce, or remedy unequal treatment of individuals or groups based on protected characteristics such as race, gender, disability, or religion.
-
C.
anti-discrimination policy
An anti-discrimination policy is an organizational rule set that prohibits unfair treatment of individuals or groups based on protected characteristics and outlines procedures for prevention, reporting, and remediation of discriminatory behavior.
-
D.
regulations
chosen
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
E.
antitrust enforcement regulation
Antitrust enforcement regulation is the body of laws, policies, and procedures through which governments prevent, investigate, and remedy anti-competitive business practices to protect market competition and consumer welfare.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.