Triple
T21895242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill University Statutes |
E540661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institutional framework document |
C16211
|
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: institutional framework document Context triple: [McGill University Statutes, instanceOf, institutional framework document]
-
A.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
B.
public institution framework
chosen
A public institution framework is a structured model that defines the principles, governance, processes, and accountability mechanisms guiding how public organizations operate and deliver services to society.
-
C.
foundational framework agreement
A foundational framework agreement is a high-level, overarching contract that establishes the core principles, structures, and long-term terms under which more detailed or specific agreements will be developed and executed.
-
D.
federal government framework
A federal government framework is a structural system that defines how power, responsibilities, and relationships are distributed and coordinated between a central authority and its constituent regional or state governments.
-
E.
legal-political framework
A legal-political framework is the structured system of laws, institutions, and governing principles that defines how power is distributed, exercised, and constrained within a society.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:07 p.m.