Triple
T16771266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audit Committee of the Board of Governors of McGill University |
E407601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university board committee |
C4031
|
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: university board committee Context triple: [Audit Committee of the Board of Governors of McGill University, instanceOf, university board committee]
-
A.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
-
B.
scholarly committee
A scholarly committee is a group of experts convened to evaluate, guide, and make decisions on academic matters such as research quality, curriculum, or institutional policies.
-
C.
board committee
chosen
A board committee is a small, specialized group of board members delegated specific responsibilities to support the board’s governance, oversight, and decision-making functions.
-
D.
university association
A university association is an organized group within a higher education institution that brings together students, staff, or alumni around shared academic, professional, cultural, or social interests to provide support, activities, and representation.
-
E.
library committee
A library committee is a group of individuals responsible for guiding the development, management, and policies of a library’s collections, services, and resources.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.