Triple
T31047938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebec law |
E791177
|
entity |
| Predicate | usesCourtOfLastResort |
P6995
|
FINISHED |
| Object | Supreme Court of Canada |
—
|
NE NERFINISHED |
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: Supreme Court of Canada | Statement: [Quebec law, usesCourtOfLastResort, Supreme Court of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCourtOfLastResort Context triple: [Quebec law, usesCourtOfLastResort, Supreme Court of Canada]
-
A.
hasNumberOfCourtsOfLastResort
Indicates the quantity of highest-level judicial courts (courts of last resort) that an entity possesses or is associated with.
-
B.
usedCourt
chosen
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
C.
confirmedToSupremeCourtOn
Indicates that an individual was officially approved and appointed to serve on the Supreme Court on a specific date.
-
D.
hadJusticeOfHighestCourt
Indicates that an entity was served or presided over by a particular justice of the highest court.
-
E.
hasAppellateJurisdictionIn
Indicates that one legal authority has the power to review and decide appeals arising from cases within a specified court, region, or jurisdiction.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 9 p.m.