Triple
T21895284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate Committee on Academic Policy and Planning |
E540662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic planning committee |
C41838
|
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: academic planning committee Context triple: [Senate Committee on Academic Policy and Planning, instanceOf, academic planning committee]
-
A.
college committee
chosen
A college committee is a formally organized group within a college composed of faculty, staff, and sometimes students, tasked with deliberating on specific academic or administrative issues and making recommendations or decisions to support institutional governance and operations.
-
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.
academic administrator
An academic administrator is a professional responsible for planning, organizing, and overseeing the non-teaching operations and policies of educational institutions to support their academic mission.
-
D.
student affairs committee
A student affairs committee is a group responsible for overseeing, supporting, and improving students’ non-academic experiences, services, and well-being within an educational institution.
-
E.
research committee
A research committee is a group of appointed individuals responsible for evaluating, guiding, and overseeing research activities, proposals, and policies within an organization or institution.
- 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.