Triple
T30727127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNG |
E782308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university system of Georgia institution |
C8236
|
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 system of Georgia institution Context triple: [UNG, instanceOf, university system of Georgia institution]
-
A.
college of the University of Georgia
A college of the University of Georgia is an academic division within the university that organizes related departments and programs to deliver specialized education, research, and service in a particular field or set of disciplines.
-
B.
state university system
A state university system is a coordinated network of public higher education institutions within a state, governed by a central authority to manage funding, policy, and academic standards.
-
C.
university system
chosen
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.
-
D.
Middle Georgia State University campus
Middle Georgia State University campus is a multi-site higher education environment comprising academic buildings, student housing, recreational facilities, and support services designed to support learning, research, and campus life across central Georgia.
-
E.
school of Georgia Tech
A school of Georgia Tech is an academic unit within the institute that organizes related disciplines, faculty, and programs under a broader college to deliver specialized education and research.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:37 p.m.