Triple
T32483335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trent University Facilities Management |
E830172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campus operations unit |
C8231
|
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: campus operations unit Context triple: [Trent University Facilities Management, instanceOf, campus operations unit]
-
A.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
B.
university organizational unit
A university organizational unit is a formally defined subdivision of a university—such as a college, school, department, or institute—responsible for managing specific academic, administrative, or research functions within the institution.
-
C.
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.
-
D.
campus facility collection
A campus facility collection is an organized set of physical spaces, buildings, and infrastructure on an educational campus that together support academic, residential, recreational, and administrative activities.
-
E.
operational unit
chosen
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:58 a.m.