Triple
T12170095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Registrar of the Supreme Court of Canada |
E289937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | court administrative body |
C8184
|
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: court administrative body Context triple: [Office of the Registrar of the Supreme Court of Canada, instanceOf, court administrative body]
-
A.
Judicial body
A judicial body is an official group or institution empowered by law to interpret and apply legal rules, resolve disputes, and administer justice.
-
B.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
-
C.
judicial administrative office
chosen
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
D.
internal administrative body
An internal administrative body is an organized group within an institution responsible for managing, coordinating, and overseeing its internal operations, policies, and support functions.
-
E.
quasi‑judicial body
A quasi-judicial body is an administrative or regulatory entity that has powers and procedures resembling those of a court, enabling it to interpret laws, conduct hearings, and make binding decisions or recommendations in specific areas of public or private disputes.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.