Triple
T21895243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill University Statutes |
E540661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | McGill University policy document |
C45476
|
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: McGill University policy document Context triple: [McGill University Statutes, instanceOf, McGill University policy document]
-
A.
McMaster University facility
A McMaster University facility is any physical or virtual space, building, or infrastructure owned, leased, or operated by McMaster University that supports its academic, research, administrative, or student-life activities.
-
B.
McGill University building
A McGill University building is a physical structure owned or operated by McGill University that provides space for its academic, research, administrative, residential, or student-life activities.
-
C.
college of the University of Toronto
A college of the University of Toronto is a semi-autonomous academic and social community within the university that provides students with residence options, advising, programming, and a distinct intellectual and cultural environment.
-
D.
Wilfrid Laurier University campus
Wilfrid Laurier University campus is a mid-sized, community-oriented academic environment featuring a compact layout of classrooms, residences, green spaces, and student facilities that foster close connections and active campus life.
-
E.
University of Victoria initiative
A University of Victoria initiative is a coordinated program or project led or endorsed by the university to advance its academic, research, community, or strategic goals.
- F. None of above. chosen
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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:07 p.m.