Triple
T36451452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-I-Z Z-O-U chant |
E898021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | University of Missouri tradition |
C66227
|
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 Missouri tradition Context triple: [M-I-Z Z-O-U chant, instanceOf, University of Missouri tradition]
-
A.
Duke University tradition
A Duke University tradition is a recurring, community-valued practice or ritual—often tied to campus life, athletics, or institutional history—that fosters shared identity and continuity among Duke students, alumni, and affiliates.
-
B.
Missouri Tigers athletics
Missouri Tigers athletics represents the intercollegiate sports programs of the University of Missouri, competing primarily in NCAA Division I as a member of the Southeastern Conference (SEC).
-
C.
University of Mississippi sports team
The University of Mississippi sports team, known as the Ole Miss Rebels, represents the university in NCAA Division I athletics, competing in a variety of men's and women's sports within the Southeastern Conference.
-
D.
Rutgers University tradition
A Rutgers University tradition is a recurring, community-valued practice or ritual—often tied to campus history, events, or symbols—that fosters shared identity and continuity among Rutgers students, alumni, and affiliates.
-
E.
Texas A&M University tradition
A Texas A&M University tradition is a long-standing, community-embraced practice or ritual that reflects and reinforces the university’s core values, history, and shared Aggie identity.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.