Triple
T459002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academic Senate of UC Berkeley |
E7295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body of a university |
C172
|
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: governing body of a university Context triple: [Academic Senate of UC Berkeley, instanceOf, governing body of a university]
-
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.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
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.
-
D.
higher education organization
A higher education organization is an institution that provides post-secondary academic or professional education, conducts research, and grants recognized degrees or certifications.
-
E.
private university
A private university is a higher education institution that is independently funded and operated, primarily through tuition, donations, and endowments rather than direct government support.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.