Triple
T28267376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Canada |
E712741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government service delivery organization |
C3213
|
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: government service delivery organization Context triple: [Service Canada, instanceOf, government service delivery organization]
-
A.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
B.
government-backed organization
A government-backed organization is an entity that operates with financial support, authorization, or guarantees from a government to carry out specific public, economic, or policy-related functions.
-
C.
government ministry
A government ministry is a specialized administrative department within a government, headed by a minister, responsible for formulating and implementing public policies in a specific sector such as health, education, or finance.
-
D.
government operation
Government operation is the coordinated set of activities, processes, and procedures through which a government implements laws, delivers public services, and manages public resources to achieve policy objectives.
-
E.
public administration body
chosen
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:15 p.m.