Triple
T12597701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutual Sports |
E300774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports radio program brand |
C2860
|
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: sports radio program brand Context triple: [Mutual Sports, instanceOf, sports radio program brand]
-
A.
sports radio station
chosen
A sports radio station is a broadcast outlet that primarily delivers live sports coverage, commentary, analysis, and related programming to listeners via terrestrial or digital radio.
-
B.
radio brand
A radio brand is a conceptual class representing a company or label that designs, manufactures, and markets radio receivers and related audio products distinguished by a specific name, logo, and product identity.
-
C.
digital radio brand
A digital radio brand is a conceptual class representing a company or label that designs, produces, and markets digital radio devices or services distinguished by shared identity, features, and positioning in the audio technology market.
-
D.
radio sports broadcasting package
A radio sports broadcasting package is a bundled set of audio production elements, rights, and services—such as live commentary, pre- and post-game shows, jingles, and sponsorship spots—designed to deliver complete radio coverage of sporting events.
-
E.
sports podcast
A sports podcast is an audio program that regularly discusses, analyzes, and comments on sports events, teams, athletes, and related news, often featuring expert opinions, fan perspectives, and interviews.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:08 p.m.