Triple
T38130593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International House at the University of Toronto |
E952209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student services centre |
C19261
|
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: student services centre Context triple: [International House at the University of Toronto, instanceOf, student services centre]
-
A.
student support service
A student support service is an institutional resource that provides academic, emotional, financial, and practical assistance to help students succeed and well-being throughout their educational journey.
-
B.
university centre
chosen
A university centre is a dedicated facility or organizational unit within a university that provides specialized services, resources, or programs to support academic, research, or student-focused activities.
-
C.
admissions service
An admissions service is a system responsible for managing and processing applications, evaluating eligibility, and coordinating decisions for entry into an institution, program, or organization.
-
D.
campus auxiliary service
A campus auxiliary service is a non-academic support operation (such as housing, dining, bookstores, or transportation) that provides goods and services to the campus community, typically funded through user fees rather than tuition or state appropriations.
-
E.
career services office
A career services office is a campus-based resource center that provides students and alumni with guidance, tools, and opportunities to explore careers, develop job-search skills, and connect with employers.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.