Triple
T33135818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syracuse Orange women’s track and field |
E848001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syracuse Orange athletic program |
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 Orange athletic program Context triple: [Syracuse Orange women’s track and field, instanceOf, Syracuse Orange athletic program]
-
A.
Syracuse University athletic team
chosen
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.
college at Syracuse University
A college at Syracuse University is a major academic division that houses related departments and programs, offering undergraduate and graduate degrees within a specific disciplinary or professional focus.
-
C.
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.
-
D.
University of Connecticut sports team
A University of Connecticut sports team is an organized collegiate athletic squad representing the University of Connecticut in intercollegiate competitions under NCAA and conference governance.
-
E.
person from Syracuse
A person from Syracuse is an individual whose origin, residence, or strong personal association is with the city of Syracuse, whether in New York, USA, or Sicily, Italy.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:27 a.m.