Triple
T25624725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston University athletic facilities |
E642396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university athletic infrastructure |
C242
|
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 athletic infrastructure Context triple: [Boston University athletic facilities, instanceOf, university athletic infrastructure]
-
A.
college sports venue
A college sports venue is a facility owned or used by a college or university where intercollegiate athletic competitions, practices, and related events are held.
-
B.
sports and recreation facility
chosen
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
-
C.
university sports competitions
University sports competitions are organized athletic events in which teams or individuals representing higher education institutions compete under standardized rules to promote physical excellence, school spirit, and intercollegiate rivalry.
-
D.
sports and education complex
A sports and education complex is a multifunctional facility that integrates athletic venues with academic and training spaces to support both physical development and educational activities.
-
E.
university sport event
A university sport event is an organized athletic competition or activity hosted by a higher education institution, involving student participants and often spectators, to promote physical fitness, school spirit, and community engagement.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:08 p.m.