Triple
T4543369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faculty of Applied Science and Engineering facilities, University of Toronto |
E109989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university faculty facilities network |
C15725
|
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 faculty facilities network Context triple: [Faculty of Applied Science and Engineering facilities, University of Toronto, instanceOf, university faculty facilities network]
-
A.
university faculty
A university faculty is a group of academic staff and scholars within a higher education institution responsible for teaching, research, and academic governance in specific disciplines or departments.
-
B.
academic facility
An academic facility is a physical or virtual space designed to support educational activities, including teaching, learning, research, and scholarly collaboration.
-
C.
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.
-
D.
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.
-
E.
science and engineering campus
chosen
A science and engineering campus is a specialized academic environment that concentrates facilities, laboratories, and resources to support education and research in scientific and engineering disciplines.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.