Jjamppong
Korean Chinese noodle soup
Jjamppong (Korean: 짬뽕) is a Chinese-style Korean noodle soup with red, spicy seafood- or pork-based broth flavored with gochugaru (chili powder). Common ingredients include onions, garlic, Korean zucchini, carrots, cabbages, squid, mussels, and pork. The dish was inspired by Chinese cuisine.
Along with jajangmyeon, it is a popular dish found predominantly in Chinese restaurants in Korea as part of Korean Chinese cuisine.
History and etymology
While the dish is derived from the Chinese Shandong-style chǎomǎmiàn (炒碼麵), the name of the dish was derived from chanpon, a Japanese Chinese cuisine dish itself derived from the Fujian-style mènmiàn (燜麵). During the Japanese occupation of Korea (1910–1945), the Japanese saw chǎomǎmiàn in Chinese restaurants in Korea and named it chanpon, as the white soup seemed similar to the soup of chanpon to their eyes. The Japanese word was subsequently adapted phonetically into Korean as jjamppong.
When considering how chanpon is made, it is assumed that the exported version of chǎomǎmiàn, a type of tāngròusīmiàn (湯肉絲麵), would have used boiled pork and chicken bones to make the broth, while the base broth of jjamppong differs in that it mainly uses stir-fried seafood and vegetables with the addition of gochugaru (chili powder) and chili oil, a practice that began in the 1960s.
Variations
In some restaurants, samseon jjamppong (삼선짬뽕) refers to a more expensive option with additional varieties of seafood. Inspired by gamja-tang, pork back-bone jjamppong (뼈짬뽕) uses a mix of pork bone broth, stir fried seafood, chili oil, and vegetables.
This brief starts where responsible research should: with the source description of “Jjamppong” as korean Chinese noodle soup. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as korean Chinese noodle soup. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 11, 2026. The linked authority identifier is Q17063016. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1910 and 1945.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Jjamppong”, its source revision and the description used here.
- Expand the search: follow Jjamppong primary sources, Jjamppong archive and Jjamppong research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Jjamppong”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Jjamppong” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.