Triple
T33688395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tartans |
E863104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carnegie Mellon University sports team collective |
C54094
|
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: Carnegie Mellon University sports team collective Context triple: [Tartans, instanceOf, Carnegie Mellon University sports team collective]
-
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 Michigan varsity team
The University of Michigan varsity team is the official intercollegiate athletic squad representing the University of Michigan in NCAA-sanctioned sports competitions.
-
C.
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.
-
D.
university athletic team collective
chosen
A university athletic team collective is an organized group that supports and manages resources, opportunities, and advocacy for student-athletes across a university’s sports programs.
-
E.
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.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.