Triple
T23846993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syracuse Orange women’s lacrosse team |
E592050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syracuse University athletic team |
C48127
|
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: Syracuse University athletic team Context triple: [Syracuse Orange women’s lacrosse team, instanceOf, Syracuse University athletic team]
-
A.
Rutgers University athlete
A Rutgers University athlete is a student enrolled at Rutgers who competes in intercollegiate sports representing the university in NCAA-sanctioned or club-level athletic 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.
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.
-
D.
University of Chicago varsity team
A University of Chicago varsity team is an officially sanctioned intercollegiate athletic squad representing the University of Chicago in competitive sports within its conference and the NCAA.
-
E.
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.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:10 p.m.