Triple
T15988459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat University Act |
E387759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | University governance framework |
C3419
|
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 governance framework Context triple: [Gujarat University Act, instanceOf, University governance framework]
-
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.
government campus
A government campus is a designated area comprising multiple buildings and facilities where various governmental departments and agencies are co-located to conduct administrative, legislative, or public service functions.
-
C.
academic framework
An academic framework is a structured set of concepts, theories, and relationships that provides a systematic lens for analyzing, interpreting, and organizing knowledge within a particular field of study.
-
D.
education policy framework
chosen
An education policy framework is a structured set of principles, goals, and guidelines that shapes how educational systems are organized, governed, funded, and evaluated to achieve desired learning and equity outcomes.
-
E.
university system
A university system is an integrated organizational framework that manages academic programs, students, faculty, resources, and administrative processes across one or more higher education institutions.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.