Triple
T20896697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Agreement on Apportionment |
E514556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian intergovernmental accord |
C23720
|
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 intergovernmental accord Context triple: [Master Agreement on Apportionment, instanceOf, Canadian intergovernmental accord]
-
A.
Canadian federal government policy
Canadian federal government policy is the set of laws, regulations, programs, and strategic decisions enacted by the national government to address public issues and guide the country’s social, economic, environmental, and international directions.
-
B.
Canadian federal bill
A Canadian federal bill is a proposed law presented to the Parliament of Canada for debate, amendment, and approval before it can receive Royal Assent and become part of federal legislation.
-
C.
Act of Parliament of Canada
An Act of Parliament of Canada is a law formally enacted by the Parliament of Canada, consisting of the House of Commons, the Senate, and the Crown, that establishes or amends legal rules applicable within Canada.
-
D.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
E.
intergovernmental consensus
chosen
Intergovernmental consensus is a collective agreement reached among multiple governments or states, typically through negotiation and compromise, that establishes a shared position or decision on a specific issue.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.