Triple
T30681692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purchase College administration |
E781067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college administration |
C1291
|
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: college administration Context triple: [Purchase College administration, instanceOf, college administration]
-
A.
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.
-
B.
academic administrative office
chosen
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
-
C.
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.
-
D.
academic college
An academic college is an educational institution or division within a university that offers structured programs of study, instruction, and research in specific disciplines leading to academic degrees or certifications.
-
E.
campus
A campus is a defined area of land that houses the buildings, facilities, and open spaces of an educational institution, supporting academic, residential, and social activities.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:32 p.m.