Triple
T26595595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UConn Huskies women's volleyball |
E667481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | University of Connecticut sports team |
C51803
|
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 of Connecticut sports team Context triple: [UConn Huskies women's volleyball, instanceOf, University of Connecticut sports team]
-
A.
Syracuse University athletic team
A Syracuse University athletic team is a collegiate sports organization representing Syracuse University in intercollegiate competitions under the Orange identity, encompassing student-athletes, coaches, and support staff across various NCAA-sanctioned sports.
-
B.
University of Arizona sports team
A University of Arizona sports team is an organized collegiate athletic squad representing the University of Arizona in intercollegiate competitions under the Arizona Wildcats banner.
-
C.
University of San Francisco athletic team
A University of San Francisco athletic team is an organized group of student-athletes representing the University of San Francisco in intercollegiate sports competitions under the school's name, colors, and regulations.
-
D.
University of Richmond sports team
The University of Richmond sports team is an organized collegiate athletic program representing the University of Richmond in intercollegiate competitions across various sports.
-
E.
Princeton Tigers sports team
The Princeton Tigers sports team represents Princeton University in intercollegiate athletics, competing in the NCAA Division I Ivy League across a wide range of men's and women's sports.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:10 a.m.