Triple
T6768293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meech Lake Accord |
E154978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian political agreement |
C964
|
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 political agreement Context triple: [Meech Lake Accord, instanceOf, Canadian political agreement]
-
A.
political agreement
chosen
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
B.
Canadian federal political position
A Canadian federal political position is an official role within the Government of Canada’s federal system, held by an elected or appointed individual responsible for national-level legislative, executive, or representative duties.
-
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.
Canadian public official
A Canadian public official is an individual who holds a position of authority or responsibility within federal, provincial, territorial, or municipal government institutions in Canada, serving the public interest and implementing laws, policies, and programs.
-
E.
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.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:12 p.m.