Triple
T21601127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research and Innovation Committee (Board of Governors, University of Calgary) |
E533042
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | board subcommittee |
C14322
|
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: board subcommittee Context triple: [Research and Innovation Committee (Board of Governors, University of Calgary), instanceOf, board subcommittee]
-
A.
board committee
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.
-
B.
governing body subcommittee
chosen
A governing body subcommittee is a smaller, specialized group formed within a larger decision-making organization to focus on specific issues, conduct detailed analysis, and make recommendations or decisions within its defined scope.
-
C.
subcommittee of a United Nations committee
A subcommittee of a United Nations committee is a smaller, specialized body established under a parent UN committee to focus on specific issues, conduct detailed analysis, and make recommendations to support the committee’s broader mandate.
-
D.
Specialized committee
A specialized committee is a focused group of individuals formed within a larger organization to address, investigate, or manage specific issues, tasks, or areas of expertise.
-
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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:32 p.m.