Triple
T475000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill Martlets |
E9041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university women's athletic program |
C51
|
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 women's athletic program Context triple: [McGill Martlets, instanceOf, university women's athletic program]
-
A.
college athletic program
chosen
A college athletic program is an organized set of sports teams, resources, and support services sponsored by a college or university to provide competitive and recreational athletic opportunities for its students.
-
B.
collegiate athletic conference
A collegiate athletic conference is an organized group of colleges and universities that compete against each other in intercollegiate sports under shared rules, governance, and scheduling agreements.
-
C.
private university
A private university is a higher education institution that is independently funded and operated, primarily through tuition, donations, and endowments rather than direct government support.
-
D.
university association
A university association is an organized group within a higher education institution that brings together students, staff, or alumni around shared academic, professional, cultural, or social interests to provide support, activities, and representation.
-
E.
collegiate athletics governance subdivision
A collegiate athletics governance subdivision is an organizational tier within a larger college sports governing body that sets and enforces rules, policies, and competitive structures for a defined group of member institutions.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.