Triple
T28170393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bliss v. Attorney General of Canada |
E715441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | equality rights case |
C14446
|
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: equality rights case Context triple: [Bliss v. Attorney General of Canada, instanceOf, equality rights case]
-
A.
gender equality case
chosen
A gender equality case is a legal or administrative proceeding that addresses alleged discrimination, unequal treatment, or systemic bias based on gender, seeking to enforce or clarify rights to equal opportunities and protections.
-
B.
LGBT rights case
An LGBT rights case is a legal proceeding that addresses alleged discrimination, unequal treatment, or violations of civil or human rights based on sexual orientation, gender identity, or gender expression.
-
C.
reproductive rights case
A reproductive rights case is a legal dispute that centers on individuals' or groups' access to, control over, and regulation of reproductive health services and decisions, such as contraception, abortion, fertility treatment, and parental rights.
-
D.
human rights case
A human rights case is a legal or quasi-legal proceeding in which an individual, group, or entity alleges that fundamental rights or freedoms protected by law have been violated, seeking recognition, remedy, or enforcement.
-
E.
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.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:12 p.m.