Triple
T19077265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill C-31 (1985) |
E466935
|
entity |
| Predicate | legalReformArea |
P17365
|
FINISHED |
| Object | gender equality in Indigenous status law |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: gender equality in Indigenous status law | Statement: [Bill C-31 (1985), legalReformArea, gender equality in Indigenous status law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalReformArea Context triple: [Bill C-31 (1985), legalReformArea, gender equality in Indigenous status law]
-
A.
legalReformer
Indicates that an entity works to change, improve, or modernize laws or legal systems.
-
B.
associatedWithLegalReforms
Indicates a relationship where an entity is connected to, involved in, or influenced by specific legal reforms or changes in law.
-
C.
reformsArea
Indicates that an entity is responsible for changing, improving, or restructuring a particular area or domain.
-
D.
areaOfLegislation
chosen
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
-
E.
legalAmendment
Indicates a formal change or modification made to an existing law, regulation, or legal document.
- F. None of above.
Provenance (3 batches)
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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e5591081908a4f8e4b2011b408 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.