Triple
T10091328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEXUS |
E215350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian government program |
C357
|
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: Canadian government program Context triple: [NEXUS, instanceOf, Canadian government program]
-
A.
Canadian government office
A Canadian government office is an administrative unit within federal, provincial, or territorial government that delivers public services, implements policies, and supports the operations of elected and appointed officials in Canada.
-
B.
Canadian public sector organization
A Canadian public sector organization is a government-funded and -controlled entity at the federal, provincial/territorial, or municipal level that delivers public services, implements policies, or regulates activities in the public interest within Canada.
-
C.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
D.
Canadian federal government department
A Canadian federal government department is a primary administrative unit of the Government of Canada responsible for developing, implementing, and managing policies, programs, and services within a specific area of national jurisdiction.
-
E.
Canadian federal commission
A Canadian federal commission is an independent or semi-independent body established by the Government of Canada to investigate, regulate, or provide expert advice on specific national issues or policy areas.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 9:01 p.m.