Triple
T12076050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Spiders |
E287550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | University of Richmond sports team |
C29944
|
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 Richmond sports team Context triple: [Richmond Spiders, instanceOf, University of Richmond sports team]
-
A.
University of Kentucky sports team
The University of Kentucky sports team is an athletic organization representing the University of Kentucky in intercollegiate competitions across various sports, most notably its nationally recognized men's basketball and football programs.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
University of Nebraska–Lincoln sports team
A University of Nebraska–Lincoln sports team is an organized collegiate athletic squad representing the university in intercollegiate competitions under NCAA and conference governance.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:48 p.m.