Triple
T15770961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fight, Fight, Fight for Washington State |
E382357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Washington State University song |
C36462
|
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: Washington State University song Context triple: [Fight, Fight, Fight for Washington State, instanceOf, Washington State University song]
-
A.
Ohio State University song
An Ohio State University song is a musical composition associated with The Ohio State University, typically performed at athletic events, ceremonies, and gatherings to express school spirit and tradition.
-
B.
Texas A&M University song
A Texas A&M University song is a musical composition officially or traditionally associated with Texas A&M that expresses school spirit, commemorates Aggie traditions, and is performed at university events and gatherings.
-
C.
Princeton University song
A Princeton University song is a musical composition, often with lyrics, that is created, adopted, or traditionally performed by members of the Princeton community to express school spirit, commemorate events, or celebrate institutional identity.
-
D.
state song
A state song is an officially designated musical composition that represents and symbolizes the identity, history, and cultural heritage of a specific U.S. state.
-
E.
Seattle University athletic program
The Seattle University athletic program encompasses the university’s intercollegiate sports teams, facilities, staff, and support services dedicated to fostering competitive excellence, academic success, and personal development for student-athletes.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.