Triple
T15246874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waves |
E364405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pepperdine University athletic team nickname |
C429
|
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: Pepperdine University athletic team nickname Context triple: [Waves, instanceOf, Pepperdine University athletic team nickname]
-
A.
athletic team nickname
chosen
An athletic team nickname is a distinctive, often symbolic name or moniker used to identify and represent a sports team in competition and fandom.
-
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.
Purdue University nickname
The Purdue University nickname represents the informal moniker or set of monikers (such as "Boilermakers") commonly used to identify and refer to Purdue University, its athletic teams, and its community.
-
D.
University of Arizona sports team
A University of Arizona sports team is an organized collegiate athletic squad representing the University of Arizona in intercollegiate competitions under the Arizona Wildcats banner.
-
E.
UC San Diego Tritons athletic program team
The UC San Diego Tritons athletic program team represents the University of California, San Diego in intercollegiate sports, fielding multiple men's and women's varsity teams that compete primarily at the NCAA Division I level.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.