Triple
T7099420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USC Trojans baseball |
E165415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | USC Trojans athletic program team |
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: USC Trojans athletic program team Context triple: [USC Trojans baseball, instanceOf, USC Trojans athletic program team]
-
A.
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.
-
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.
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 football team
A university football team is an organized group of student-athletes representing their institution in competitive American football, typically governed by collegiate athletic associations and supported by the campus community.
-
E.
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.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:42 p.m.